The question isn’t whether to plan in a room or in software. Hoshin planning needs both, and most problems come from using one for the other’s job: running catchball across sites from a workshop, or drafting a strategy in a form field.
In this guide
Key Takeaways
- →A room is for thinking together. A system is for a durable record and many participants over time.
- →Breakthroughs, cuts and correlation grading belong in the room. Catchball, cascade and lock belong in the system.
- →Photographs of whiteboards hold the outcome, not the reasoning. That is what next year’s reflection needs.
- →Don’t let the tool’s structure drive the conversation. Facilitate in the room, capture in the tool.
- →The test of a good combination is that there is no transcription step after the offsite.
- →First cycle with no record yet? A workshop and a spreadsheet are a reasonable start.
Two tools, two jobs
Some organizations plan entirely in the room: whiteboards, sticky notes, an X-matrix drawn by hand and photographed at the end. Others try to do the whole cycle in software, with executives clicking through forms. Both work less well than a combination, because each medium is good at different stages.
A room is good at what needs people thinking together: weighing evidence, debating priorities, making hard cuts. Software is good at what needs a durable record and many participants over time: reflection, catchball across levels, locking and running the plan.
Which stage belongs where
| Stage | Best medium | Why |
|---|---|---|
| Reflect | Software, then a room | The evidence is assembled from the record; the verdicts are agreed in conversation |
| Breakthroughs | Room | A small group debating direction |
| Annual objectives and vital few | Room, captured live in software | Debate and cuts need the room; the output needs to persist |
| Correlate and gate | Room, captured live in software | Grading is a conversation; the grades become records |
| Catchball | Software | Many participants, several rounds, weeks long, needs visible status |
| Cascade | Software | Many levels and sites working in parallel |
| Lock and deploy | Software | The locked plan must be the operating plan |
Those are the seven stages of the hoshin kanri planning cycle, sorted by medium rather than by sequence.
Where workshops fall short
- The record. Photographs of whiteboards hold the outcome, not the reasoning. By the next cycle, nobody remembers why a target was set where it was.
- Catchball beyond the room. Once the plan leaves the offsite, a workshop-only process falls back on email, with all the delays and invisibility that brings.
- Transcription. Someone has to type the wall into a spreadsheet afterwards, and things change in translation.
Where software falls short
- Blank-sheet thinking. Forms are poor at helping a group think about direction. Breakthrough debates belong in a room.
- Hard cuts. Deciding which priorities don’t make the list is a social act. It needs people looking at each other, not at screens.
- Demo-driven planning. When the tool is new, there’s a temptation to let its structure drive the conversation. Facilitate in the room; capture in the tool.
Think in the room. Record in the system. Run the year from the record.
A practical combination
- Reflection prepared from the record before the offsite, not reconstructed during it.
- Offsite facilitated in the room, with one person capturing decisions live in the planning tool.
- Catchball moved to the tool on the last afternoon of the offsite.
- No transcription step. What leaves the room is already in the system.
If this is your first hoshin cycle and there’s no record yet, a workshop and a spreadsheet are a reasonable start. See Your first hoshin planning cycle.
A worked example: one planning season, two media
| Weeks | Activity | In the room | In the system |
|---|---|---|---|
| 1 to 2 | Reflection | Verdict conversations with each pair of owners | Evidence drawn from the record; verdicts recorded |
| 3 | Breakthroughs | Executive session | Breakthroughs confirmed on their multi-year records |
| 4 to 5 | Offsite | All debate, ranking and cuts | Decisions captured live by one person |
| 6 to 9 | Catchball | Meetings only when a thread stalls | Sessions on every objective; status visible |
| 10 | Cascade | Site workshops for pilot sites | Site objectives linked to group priorities |
| 11 to 12 | Lock and deploy | Lock session | Phasing, owners and cadence set |
Illustrative.
The room carries the heavy thinking in weeks 3 to 5. The system carries everything that involves many people over time. Nothing is typed up after the offsite, because nothing was left on the wall.
What the software half has to do
The fourth bullet of the practical combination is the whole product specification: no transcription step. A tool that cannot be edited at the speed of a room forces one, and the moment someone types the wall into it afterwards, every weakness listed under workshops comes back. The reasoning is lost in translation, and the system holds an outcome nobody can defend.
So the question to ask a vendor is not whether it can store an X-matrix. It is whether twenty people can watch one person build the matrix while they argue about it, and whether what they argued about survives.
| What the room hands over | What the tool has to do with it | How to test it in a demo |
|---|---|---|
| Verdicts on last year | Hold a verdict and a reason per correlation, across years | Open a closed year and show me its verdicts |
| A priority cut from the list | Keep it visible as deferred or stopped, with the reason | Drop a priority and show me where it went |
| A correlation graded in the room | Store grade, mechanism, contribution, lag window, kill signal | Click a dot and show me what opens |
| A target proposed to the level below | Open a dated negotiation thread on that objective | Start catchball and set a round close date |
| Weeks of parallel negotiation | Show the planning lead which threads are open, agreed or stuck | Show me six sessions at once and their status |
| The locked plan | Become the operating plan, with phased values and a cadence | Lock it, then show me January’s review running from it |
Row 1 is what makes next year’s room better than this year’s.
Rows 4 and 5 are where a workshop-only process actually breaks, rather than merely being inconvenient. Catchball runs for four weeks across dozens of people; email cannot show the planning lead where the plan stands, so the calendar slips. The structure that keeps it inside four weeks is in running catchball rounds, and what the negotiation should leave behind in catchball in software.
Row 6 is the one that decides whether the two media stay joined after January. A plan that locks in a document and is then rebuilt as a reporting pack has quietly become two plans. Hoshin kanri software vs Excel covers where that split usually appears.
What each half costs
The room is the expensive half and nobody questions it. Twelve to twenty senior people for three days, travel, preparation and facilitation runs to a substantial annual figure, spent whether the offsite produces a defensible matrix or a set of photographs. A tool that removes the transcription week and keeps the reasoning is being compared against that number, not against zero.
On the software side the published models differ mainly in how many people they let in. OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. Rows 4 and 5 of the table above are the relevant test: catchball involves the level below and, in a cascade, the sites. A model that charges per seat prices the half of the process that software is specifically better at.
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Hoshin Kanri sits in Essentials with OKRs and Goals, Balanced Scorecard and Strategy Roadmap, which matters for the last row: the locked plan becomes the operating plan, and the teams carrying each priority run their quarters on the same data model rather than in a second system. What drives the cost of hoshin kanri software lists the rest to total, and the seven pass/fail tests the questions to ask.
The 30-day free trial covers a full offsite and the first catchball round, which is the span where the two media have to hand over to each other cleanly.
The combination in Profit.co
Profit.co is built for the software side of this split. The X-matrix, graded correlations and objectives can be entered live during the offsite, catchball sessions open on each objective for the weeks that follow, and the locked plan runs through check-ins, huddles and the bowler chart from the start of the year. Last year’s record, viewable across years, prepares the reflection. More on the planning software page.
Read against the four-point combination, that is each point with somewhere to land. The reflection is prepared from check-in histories rather than reconstructed. The offsite has one person capturing into the same matrix the year will run on. Catchball opens on the last afternoon rather than the following week. And there is no transcription step, because what the room agreed is already the record.
Free Product Demo
Prepare your offsite from the record
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
Both. Use the room for debate and hard choices, capture decisions live in software, and run catchball, cascade and the locked plan in software.
Keeping the reasoning behind decisions, running catchball beyond the room, and avoiding a transcription step afterwards.
Blank-sheet thinking about direction and the social act of cutting priorities, which both need people in a room.
Yes, and that is the test of a good combination. One person captures decisions as the room makes them, so nothing is typed up afterwards and the reasoning is not lost in translation.
Not necessarily. With no record to draw on, a workshop and a spreadsheet are a reasonable start. The payoff arrives in cycle two, when the reflection needs last year’s verdicts and reasoning.
At catchball. It runs four weeks across dozens of people at several levels, and email cannot show the planning lead which negotiations are open, agreed or stuck.
