From the design of your teams and your governance through to putting it in place, so the plan gets delivered.
Recognise two or more? Then 30 minutes is enough to know the smallest first step.
We do not guide a move that was prepared by others. The design and the implementation belong together with us, because we steer the implementation on what the design promised.
Book a conversationThree interventions in central departments, described by sector and type.
An internal service desk for the small requests and one intake for the rest. Lean working and the removal of waste took the team from 19 to 13 people, at the same lead time and quality.
Application management split from project management, and the first line moved to the service desk. The team went from 17 to 15 full-time staff, and the application managers could advise their business units with data on run and build.
A PMO on PRINCE2 and Scrum in a department of around a hundred people, with reporting on run and build costs that can be compared across projects.
Whoever has to carry a change helps design it. That is why we work with a design group, with participants from the teams involved.
People who know the work, and time in their diaries. They are the ones who carry the design afterwards.
Usually that is you. You give the assignment and stay the owner of the question of where it gets stuck today.
Decides the order of what matters, and gives the go-ahead to refine.
Five to ten people who map out in a series of working sessions what the organisation is going to look like.
A wider group that sees where we stand every second or third session and asks the critical questions. That way the design does not come out of the working sessions as a surprise.
The participants for both groups come out of the conversations. We put in the knowledge that is needed, from the supporting departments too, and people from different levels in the organisation. Including those who are critical of it, because whoever is not yet convinced asks the questions that make the design stronger.
Four phases. The model comes at the end, never at the beginning.
Before we design anything, we know what is going on and who is thinking along.
We start from your strategic plan: which work and which information have to move differently through the organisation to deliver it. Together we set the scope and which part we take on first, and from that follows who we talk to. Those conversations produce three things: the strategic trade-offs, the criteria by which the work is divided, and the dependencies between teams. And they almost always produce one more: the places where your plan is read differently. That is rarely a conflict, it simply does not show until you put those differences side by side. Those same conversations also produce the participants for the steering group and the design group.
First what matters, then the extremes, and only then what is feasible.
We put side by side how your organisation is arranged today and how it needs to be arranged. The design group works out what really matters for realising your strategic IT plan. Is it closeness to the business? Clear standards? Clarity about who does what? And what your department sets out for itself counts just as heavily: depth of craft you do not want to lose, security that stays covered, people with somewhere to grow. The design group records those points and puts them in order, so that it is settled what a model is weighed against and what matters most in your strategic IT plan can carry weight in the design. The steering group confirms that order. The group then draws, for each criterion, the model that scores highest on it, even where that is not feasible for you. Those extremes show what each choice costs. Only then does it build the scenarios that are feasible, with a preferred one. The sounding board group sees where we stand along the way and asks its questions.
Whoever helped make the design also makes the plan to put it in place.
The steering group gives the go-ahead to refine. The sounding board gives feedback and is invited to help refine. The same design group works it out: per team and per level what it has to do, what it decides on its own, and where it has to align with another team. That is the answer to the question everyone asks as soon as something changes. After that comes the implementation plan, and we put that to the sounding board and the steering group again.
Until the new way of working is the ordinary way of working.
The plan is carried out by your managers and your teams, and we stay with it. We do not take the work over. We steer where practice turns out different from paper. We set the expected benefits against what is measured and steer on the difference. The same people from the design group stay involved, so the questions that come up along the way reach those who helped make the choices. The sounding board sees what of the design holds up. We stop when the new way of working is the ordinary way of working, not when the plan has been delivered.
What would this engagement look like at your organisation?
Book a conversationFrom the first conversation to a design with an implementation plan, count on three to four months. Putting it in place takes until the new way of working is the ordinary way of working, usually two to four quarters. Where your engagement falls in that range we estimate in the first conversation.
The portfolio practice is part of this service. You can also take it on its own, if your organisation stays as it is and only the view of it and the decision making have to change.
Governance at the level where it belongs, from portfolio to community of practice, so you see in one place whether your plan is progressing. Even without your organisation being redesigned.
Read about this serviceIn it we look at where your strategic plan gets stuck today. You get our view of what is going on and a proposal for the smallest first step.
Or email contact@cohentis.be, or call 02 455 07 94.