Practical guides
16 short, practical guides for clearer roles, faster decisions and smoother change. Each one ends with a free tool you can use straight away.
Roles and ownership
One Accountable owner, always
If two people are accountable, nobody is. Unclear ownership is one of the most common reasons work stalls between teams.
- List your ten most frequent activities.
- Name a single Accountable person or role for each one.
- Name who is Responsible for doing the work.
- Add Consulted and Informed roles only where they genuinely need to be involved.
- Discuss any disagreement openly. It usually shows where ownership really is unclear.
Write a RACI people will actually use
A RACI that lists every task becomes unreadable and gets ignored. Keep it at the level where ownership questions actually arise.
- Use activities and decisions, not detailed tasks. Ten to fifteen rows is usually enough to start.
- Use roles instead of names so it survives reorganizations.
- Limit Consulted to people who must give input before the work or decision proceeds.
- Walk through it with the people named and fix what they dispute.
- Review it whenever teams or responsibilities change.
Turn a RACI into role profiles
Once ownership is agreed, a short role profile makes it durable for hiring, onboarding and performance conversations.
- State the purpose of the role in one or two sentences.
- List the key accountabilities taken from the RACI.
- Write down what the role decides, recommends and is consulted on.
- Name the main interfaces with other teams.
- Add two or three measures of success.
Decisions and governance
Fix the five slowest decisions first
You don't need to map every decision. Start with the ones that visibly stall and cost the most time.
- Pick the five decisions that most often wait or get reopened.
- For each, record who decides, who recommends, who must be consulted and who is informed.
- Set a target turnaround and an escalation path.
- Compare target with actual time and look for over-consultation.
- Review again after a month and adjust.
Audit your governance forums
Meetings and councils accumulate over time. A simple audit shows which ones still earn their time.
- List every recurring forum with its owner, cadence and attendees.
- Write down the purpose and the decisions or outputs each one produces.
- Mark forums with no decision outcome or with similar purposes.
- Merge, shrink or retire the weakest candidates.
- Set a review date so the list stays current.
Keep a simple decision record
Teams often re-argue decisions because nobody wrote down what was decided and why. A short record prevents that.
- Record the date, the decision owner and the status.
- Summarize the context and the constraints.
- List the options considered, with pros and cons.
- State the decision and the rationale.
- Note the actions that follow, with owners and dates.
Centralized, federated or hybrid: how to choose
There is rarely a single right answer. The useful question is which trade-offs your organization can live with.
- Agree the criteria first, such as cost, speed, risk, service quality and change effort.
- Weight the criteria by what matters most right now.
- Score each option and look at where each is strong or weak.
- Test the result with the leaders affected, because scores are judgments.
- Pilot before committing across the whole organization.
Process and handoffs
Run a focused current-state assessment
A good assessment is short, evidence-based and ends with options, not just a list of problems.
- Agree scope, questions and the people to involve.
- Gather views through interviews, documents and a short pulse survey.
- Map roles, decision rights, forums and key handoffs.
- Group the findings into pain points, duplication, bottlenecks and gaps.
- Present options with trade-offs and a recommended next step.
Map one handoff end to end
Handoffs between teams are where delays and rework hide. Start with a single process that clearly struggles.
- Choose one process that often stalls or produces rework.
- Walk it step by step with the people who do each part.
- For each handoff, record the inputs, outputs, timing and owner.
- Agree what the receiving team can expect from the sending team.
- Fix the biggest handoff first and measure the change.
Find duplicated work across teams
The same capability often exists in several places under different names. Naming capabilities consistently makes duplication visible.
- List what each team does, as capabilities rather than job titles.
- Group them on one capability map.
- Look for the same capability owned in more than one place.
- Decide whether to centralize, standardize or keep each one local, and write down why.
- Check that the owner of each capability is clear.
Change and adoption
Run a 90-minute alignment workshop
A short, structured session can align leaders faster than a series of one-to-one conversations.
- Send a pre-read two days ahead with the objective and the questions.
- Spend the first ten minutes agreeing the goal.
- Capture pain points, then narrow to a shortlist of options.
- Finish with decisions, owners and dates.
- Keep a parking lot for topics that need another forum.
Plan adoption before the announcement
People support changes they understand and feel ready for. Readiness is easier to build before an announcement than after.
- List every group the change affects.
- Rate the impact on each group and how ready it is today.
- Brief managers before the wider announcement and give them clear talking points.
- Plan a message, channel and sender for each group.
- Track what has been sent and revisit groups with low readiness.
Measurement and learning
Run a transformation log
Programs lose momentum when actions, decisions and risks live in different documents and inboxes.
- Keep actions, decisions, risks and issues in one log.
- Give every item an owner, a due date and a priority.
- Review overdue, blocked and high-priority items every week.
- Send leadership a short update drawn from the same log.
- Close items explicitly so the log stays trustworthy.
Choose a few operating metrics
Too many measures hide the signal. A small set that people actually review works better.
- Pick three to five measures for each workstream.
- Mix outcome measures with health measures, such as decision time or handoff delays.
- Record a baseline before you change anything.
- Name an owner and a review cadence for each measure.
- Drop measures nobody uses.
Capture lessons so they get reused
Lessons written once at the end of a project are rarely read. Capture them as you go and make them easy to find.
- Record lessons at milestones, while they are fresh.
- Say what happened and what to do differently next time.
- Tag each entry by category and initiative.
- Review the repository at the start of the next initiative.
- Turn recurring lessons into templates or standards.
Moving to a product operating model: start small
A shift from projects to products touches funding, ownership and governance. A pilot lets you learn before scaling.
- Choose one or two product lines for a pilot.
- Name one accountable product owner for each.
- Align funding and governance to the pilot, with compliance checkpoints built in where needed.
- Measure outcomes, not just delivery.
- Adjust from what you learn, then extend to other lines.
Want these applied to your organization?
Book a free 30-minute review and we will work out where to start.
Work with us