Skip to content

[Role vs Skill]

We know that team liquidity (the ability to match knowledge work and knowledge worker) is one of the significant sources of delays in value streams. We also know that one of the biggest challenges to increase team liquidity is seeing skills as roles.

1 min read

Originally posted on LinkedIn · 31 reactions · 1 comments · View original →

[Role vs Skill]

[Role vs Skill] We know that team liquidity (the ability to match knowledge work and knowledge worker) is one of the significant sources of delays in value streams. We also know that one of the biggest challenges to increase team liquidity is seeing skills as roles.

What do you need?

  • A Product Owner or Product Ownership?
  • A User Experience Designer or User Experience Design?
  • A Tester or Testing?
  • A Business Analyst or Business Analysis?

I've been experimenting with a model to visualise and use the concept of team liquidity more strategically.

The model builds on top of Troy Magennis' work, blending it with David Anderson's Fit-for-Purpose and Kanban concepts.

Our current assumption on the unique context we're experimenting with is that the healthy range for the Liquidity Index is between 50% and 75%.