Network structure – 11 lessons learned

Posted on Leave a commentPosted in management

1. Autonomous & multifunctional teams

Having all necessary skills in one place allows you to have hyper performing teams able to handle complex tasks. This can be achieved if such environment is created for teams:

  • Ability to make decisions on a timely manner and with maximum return on value
  • Technical and organizational autonomy to deliver on demand
  • Focus on clearly defined area to avoid context switch
  • Possibility to acquire all required skillset to enable autonomy and reduce dependencies
  • Service oriented approach which brings value both internal and external

2. Value/Service delivery oriented teams

Main benefit of such setup is reduction of functional/component (which typically are valuable only in combination) dependencies because teams are forced to exchange valuable services with each other.

Important to keep in mind that it is still a system of mutually dependent elements. It means that it is crucial to operate with respect to the capacity of the teams that you are dependent on. Negative effect of sub-optimization is amplified by fast pace of autonomous network elements.

It requires to adjust behavior, and instead of putting all effort on performing local optimizations to advocate and strive for solving identified bottleneck in the whole structure.

One sample could be hiring. Instead of hiring into your area, hire where bottleneck is or even form a new missing entity. Such actions will optimize whole value delivery

3. Common target

Whole activity of a network must be aligned to a common target. If there is no common goal defined network structure will perform only slightly better comparing to conventional organization (where each function optimizes it’s behavior according their KPIs). Positive effect is driven by focus on value delivery for identified users.

Even if you do not utilize all benefits of network structure you at least will achieve following:

  • Clear cost structure: teams are organized around value delivery and 100% focused on a single purpose
  • Clear communication map: easy to understand who is covering which areas
  • Easier to notice not covered areas, dependencies and

You can make a decision on a strategic level in <10 minutes for a scale of 400 people by just looking at a couple of pages in confluence (or other team collaboration solution) without diving into complex excel files and diagrams.

4. Strive on being a team

It is important to take personal responsibility for every leader of network element and make an effort to act as a team. Team typically shares following characteristics as minimum (if compared to a group):

  • aligned goal,
  • optimizing the whole,
  • supporting

5. Fire fast

The only way to save the box of apples is to throw away rotten ones. By “rotten” in this context I mean:

  • not acting upon achieved agreements,
  • acting according own agenda,
  • not adapting behavior according raised expectations,
  • not learning.

6 Constraints

No system cannot operate without constraints. It is needed to eliminate entropy and to keep the focus of the whole. The most important constraint is common target.

Other constraints play key role in establishing stability because they set rules for communication between elements.

Includes, but not limited to: organizational level artifacts and deliverables, KPIs and/or Service Level Objectives, agreements, dependencies, set of internal services. Each element must expose following artifacts publicly available:

  • Purpose aligned with common target
  • List of stakeholders (clients and dependencies)
  • Service/Product catalog
  • Team structure
  • Roadmap
  • Business KPIs
  • SLOs and Non functional requirements
  • High-level architecture

7. Quality

Quality must never be opinion based. It must be measurable and agreed set of clearly defined metrics that are communicated to stakeholders, publicly visible and tracked in real-time.

There always must be a professional included in a team who understands what quality assurance as discipline means and knows all set of practices that can and should be applied at the right moment of product/team evolution.

Typical mistake is to measure quality with # of bugs. If your team relies mainly (or sometimes only) on this metric, it means there is no agreed quality definition in the team.

Things mentioned are important and beneficial for conventional structure, but vital for network structure because of service oriented approach.

8. Internal services/platforms are critical

It is critical to establish and properly staff internal service/platform teams as soon as possible. It will increase speed and efficiency of the rest of organization. Such internal services cannot be avoided and must be used across company.

It can be useful (time to market, lack of experience and etc.) to use 3d party vendors or build custom solution as a temporary decision while internal service is being developed.

9. “API”

This is foundation of network structure. Contexts must be separated by programming interfaces. It gives possibility to:

  • have autonomous teams,
  • control dependencies with other teams,
  • react faster to market needs due to proper technical decomposition,
  • apply the best technologies and tools for specific challenge,
  • reduce unnecessary communication and coordination (the most important!) among teams,
  • easily add more teams with increasing returns,
  • keep innovating and reduce unknown side effects due to smaller codebase.

10. Chaos in da house

Assumptions that things do not change and can be finalized are wrong. It applies both for work structure and technical solution.

Way of work. Network structure is dynamic as it consists of autonomous elements not fixed functions which can be changed/adjusted based on business needs.

Technical uncertainty. Capacity, stress and resilience tests are new practices that must be introduced and performed periodically. This is the only approach that will help to: ensure technical excellence, identify bottlenecks, visualize dependencies and ensure right level of automation in all teams.

11. Building an internal service/platforms is difficult

Because it requires to act differently (not typical for internal teams in conventional structure):

  • Identify users
  • Understand their problems
  • Build a solution for those problems (not ideal solution)
  • Deliver value as early as possible (typically pick to work on ideal solution)
  • Continuously work with users in gathering feedback, sharing knowledge, organizing meet-ups and etc. (the most difficult)

This is big behavioral shift from a conventional functional/component team that focuses only on development into a multifunctional team which spends a lot of time on pre and post development activities.

12. Resources that I was inspired by

Here is possible implementation of network structure – http://agilemindstorm.com/2016/03/16/network-structure-it-works/

It was inspired by following material:

Recent findings which show things are moving that direction:

APIs are important part of (network) organization

Posted on Leave a commentPosted in management

As network organization is evolutionary and must be constantly adjusted to actual value being delivered you must have evolutionary architecture. Both approaches are aimed to decompose “Big Ball of Mud …”

Even though i think it is essential for network organisation company structured in any way will benefit from this type of product architecture.

You can read more about that in this great article – https://www.thoughtworks.com/insights/blog/microservices-evolutionary-architecture

Microservices meet this definition because of its strong bounded context principle, making the logical division described in Evan’s Domain Driven Design a physical separation. Microservices achieve this separation via advanced DevOps practices like machine provisioning, testing, and automated deployments. Because each service is decoupled from all other services (at the structural level), replacing one microservice with another resembles swapping one Lego brick for another.

Network organization in a nutshell

Posted on Leave a commentPosted in management

Important

  1. Build multi-functional team.
  2. Pick up the problem/challenge/value.
  3. Define whom it’s important for.
  4. Define dependencies.
  5. Define success/failure criteria.
  6. Slice it.
  7. Prepare.
  8. Make.
  9. Give it to the world.
  10. Retrieve & analyze feedback.
  11. Keep #6, #7, #8, #9, #10 – cycle short.

Depends (not important)

  • Process you use – less is more. underestimated cost of spreading heavyweight process accross users.
  • Tools you use – bottom up standardization normally works much better. but would be interesting to make an investigation how/if tools standardization really helps.
  • Planning – as lots of work is invested into making a plan, people try to a void changing it to match the reality.
  • Various definition and templates – often do not match real work even before being issued.
  • Roles descriptions – typically defined for people below high level management.

p.s. Tayloristic organisation defines “not important” as highly important

#75 out of 100

Posted on Leave a commentPosted in management

Although i am not acting as Agile coach or trainer but surprisingly listed here – 100 Top Agile Blogs in 2015TOP 100

Happy and proud to be among great people of agile community. It will definitely encourage me to continue sharing my ideas and thoughts about how to organize work in a company to keep Agile mindset even when you grow from 20 to 600.

Posts that worth taking a look at:

Thank you for reading.