Governance models

How decisions are made and steering happens

Governance is who decides what and at what rhythm. Which forms you need follows from the team model you choose, and it is usually several at once. On top of that, how they work depends on the strategic goals you want to be able to measure and on the speed at which work and information have to flow through.

Portfolio

What we do now, what later, and what not at all.

The portfolio is the place where the organisation chooses. Not which solution, but which work happens first, which work waits and which work does not go ahead. Without that place the choice is made anyway, only scattered and invisible, by whoever shouts loudest or calls last.

Demand

How a request from the business reaches a team.

Demand management is the route from request to team. It settles who takes a request in, how it is weighed and when it lands with a team. The lighter that route, the sooner the work starts. The heavier it is, the better you can steer. Many similar requests can take a light route. Few but very different requests ask for a heavier one.

PMO

The overview and the rhythm across the engagements.

A PMO holds the overview and the rhythm: what is running, where it is stuck, and when we look at it. A PMO that mostly reports costs more than it brings in. A PMO that makes bottlenecks visible to whoever can solve them pays for itself.

Change office

Following the change itself alongside the delivery.

A change office does not follow the delivery but the change: what is asked of people, how much arrives at the same group at once, and whether it lands. That is different work from project tracking, and it rarely coincides with the project plan.

Communities of practice

People with the same craft across the teams, also called guilds.

A community of practice brings together people with the same craft across team boundaries. It works when there is a goal attached that comes from the strategy of the IT organisation, and when time has been agreed for it. Otherwise it stays at good intentions.

Centers of Excellence

Bundled expertise that teams can call on, working in the team temporarily or coaching.

A Center of Excellence bundles expertise that is too scarce to sit in every team. The difference from a staff department is the direction: the expertise comes to the team, working alongside it temporarily or coaching, instead of imposing standards from a distance.

Which form with which model

Product teams ask for a portfolio that frees up budget on goals, and agreements with the teams that have to deliver something.

Stable teams mirroring the business ask for demand management between the mirror teams and the central departments, with priorities visibly settled.

Platform teams ask for a place of their own in the portfolio and one list of work for all internal clients.

Central with local delivery asks for one set of priority rules and a view of the lead time across the whole chain.

Supporting forms ask for an agreement about time and a mandate that is named.

Where does your plan get stuck today?

In a 30 minute conversation we choose the first step together.