The choice

Standard framework or your own design

A standard framework is off the peg. We make it to measure, and where it fits we use the same cloth and the same patterns.

Off the peg

It is ready to wear and it is cheap. You adjust the way you work to the framework, and you may run into others in the same outfit.

Made to measure

Follows how your organisation is put together and what your strategy asks of it. Where it fits, we use the same cloth and the same patterns.

A framework asks you to adjust the way you work to it. A bespoke design asks you to choose what your strategy needs from your organisation.

We design in this order

Before anything large is invested, we look with you for the smallest test of an assumption.

01

Your strategy

What the new plan asks of your IT organisation, and which benefits hang on it. From on premise to cloud or the other way round, introducing CI/CD, adopting a composable architecture, or something else that answers what your business and your clients need now.

What is expected of your IT from now on? That shows what needs focus.

02

How you work today

Which services you deliver today and what your organisation has to be able to do for that. We lay that service catalogue and capability map beside the teams, roles and agreements that exist now, and beside the places where the work waits.

Where does your new strategic plan get stuck in your IT organisation today?

03

Your organisation tomorrow

The organisation model that helps realise the benefits of your plan. Responsibilities, ways of working and approach are often scattered across the organisation today, because they were set up from a previous strategic plan or simply grew that way. In the design, the work runs in one clear line through your IT organisation, with the focus of your plan translated into it: which way of working that asks for, which team form fits it, and who decides what.

From needs to form

Choosing a model starts with what your department has to be able to do. That follows from what the business asks of it and from what it sets out to be. The service catalogue and the capability map are the tools for that.

One service usually rests on several capabilities, and one capability usually carries several services. A capability therefore rarely coincides with a team, a job or an application.

Each layer follows from the one before. Turn the order around and start from the teams that exist today, and you design the set-up you already have, and you steer from your IT organisation how the business has to work.

Needs and ambitions

What the business needs from you to meet its plan, and what your department sets out to be. Depth of craft, scale, security, the development of your people.

Service catalogue

Which services stand against that, for whom, and under which agreements.

Capability map

What your organisation has to be able to do to deliver those services. A capability is not a team and not an application, it is something your organisation can do durably.

Team and governance model

Only here does the form come into view, together with the question of where those capabilities already sit today.

An example

An IT department of four hundred people, with a separate architecture department of twenty. The plan: away from a monolithic architecture, towards composable.

Composable is a building principle, not a project. So it lands in the way the teams build. That probably goes faster with product teams, and with the architects spread across those teams instead of in a department of their own.

With a Center of Excellence that sets up the governance and follows the goals around composable. The same people, a different place in the organisation, and the plan starts moving.

See all models

Where does your plan get stuck today?

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