Three days after a deal closes, someone on the integration team opens PowerPoint, pulls up the 100-day plan deck from the last acquisition, and starts swapping in the new workstream names. Five lanes — Communication, HR, Commercial, IT, Finance — stacked at equal height across three equal-width columns for Day 1-30, Day 31-60, and Day 61-100. It looks fine until the actual milestone lists come back from each workstream lead. IT has seven discrete items landing inside the first 30 days alone — system inventory, access provisioning, a data migration plan, four more — while Communication has two for the entire quarter. The fixed-height IT lane turns into a pile of overlapping diamonds and labels. The fix: size each phase column to its actual day count instead of an even third, size each lane's height to that workstream's own milestone count instead of a shared default, and group each lane as one object so adding or cutting a workstream later is a redistribute, not a rebuild.
The scenario above isn't a hypothetical. It's close to a literal description of what a 100-day plan slide looks like on the Monday after signing, before any workstream lead has actually submitted their milestones — and it's also close to what the slide still looks like a week later, after a facilitator has pasted those milestones into the same layout without changing the layout's assumptions. Three equal columns across the top, labeled Day 1-30 / Day 31-60 / Day 61-100. Five equal-height lanes down the side, one per workstream, each built as a simple horizontal bar with small diamond markers dropped in roughly where each milestone seems to belong.
The IT & Systems lane is where it falls apart first, because integration IT work is almost always front-loaded: system inventory, access provisioning, a data migration plan, a cutover rehearsal, a help-desk handoff, a legacy-system decommission date, and a go-live checkpoint can all land inside the first 30 days on a mid-size deal. Seven markers, one 30-day-wide column, one lane height that was decided before anyone knew the count. The diamonds overlap. The labels overlap worse. Meanwhile the Communication lane — a kickoff town hall in week one and an all-hands update at Day 60 — sits in a lane exactly as tall as IT's, mostly empty, because the lane heights were set once, uniformly, at the start.
Four decisions made the slide fragile, and none of them look wrong in isolation — they're just decisions made before the content existed, then never revisited once it did.
Equal column widths, regardless of actual day count. Day 1-30 and Day 31-60 are genuinely equal — 30 days each — but Day 61-100 is 40 days, not 30. Drawing all three columns at an even third isn't just cosmetically off; it under-represents how much calendar time the final stretch actually covers, which matters when a reader is trying to judge pacing at a glance.
Equal lane heights, regardless of milestone density. Nothing about a workstream's name predicts how many milestones it'll carry. On one deal IT is the crowded lane; on a carve-out, it's often Legal or Finance (entity separation, TSA exit dates, standalone ledger cutover) that balloons instead. A template that fixes every lane's height before the milestone list exists is solving a problem — "how tall should this lane be" — with an answer that has nothing to do with the actual input.
Milestones positioned by eye instead of by a shared day-to-position scale. Without a calculated reference, a marker for "Day 38" and a marker for "Day 30" tend to land in nearly the same spot, because both get placed "just after the first column starts" rather than at a measured 38% and 30% across the full track. The further a milestone's actual day is from a phase boundary, the more this eyeballing error compounds — a Day 52 milestone can end up looking identical to a Day 45 one if both were placed by feel against the nearest gridline.
Each lane built as a loose pile of shapes instead of one grouped object. When the IT lane's shapes — label, track, seven diamonds, seven labels — aren't grouped, fixing the overlap means dragging each piece individually, and inserting a sixth workstream (a Carve-Out Separation lane, say, on a divestiture-driven deal) means manually re-measuring and nudging every lane below it. This is the step that turns a five-minute edit into a forty-minute one.
Start with a ruler, not the curve or the lanes. Decide the total day span (100 is conventional, but a few integration teams run 120 or extend the final phase to a Day 90 board checkpoint — the method doesn't care which number you pick, as long as you pick it before drawing anything). Divide the track width by the total day count to get a pixels-per-day (or inches-per-day) constant, then place each phase boundary at cumulative-days × that constant rather than at an even fraction of the track.
For a standard 30/30/40 split across a 10-inch track, that puts the first boundary at 3 inches (Day 30 ÷ 100 × 10), the second at 6 inches (Day 60 ÷ 100 × 10) — not at 3.33 and 6.67, which is where "three equal columns" would put them. The difference is less than half an inch per boundary, which sounds trivial until a reader tries to eyeball how much runway Day 61-100 actually has; at equal thirds it looks like exactly as much time as Day 1-30, when it's actually a third more. Draw the two boundary lines as thin dashed verticals (light gray, 1pt), and set the phase header labels — "Day 1-30," "Day 31-60," "Day 61-100" — centered over each resulting column, sized to its own width rather than a shared font size picked for the narrowest one. The same proportional-boundary logic is what keeps a consulting-grade Gantt chart readable once task durations stop being round numbers — a 100-day plan is really a Gantt chart with exactly three phase labels painted over a day axis, and it inherits the same rule.
Don't decide lane height until the milestone list for that lane exists. Once it does, the calculation is mechanical: a lane that needs one tier of markers (no two milestones close enough on the day axis to collide) needs roughly marker height + label height + a small margin — call it 0.4 inches for a typical marker-and-label pairing. A lane whose milestones cluster — IT's seven items, five of them inside the same 30-day window — needs two tiers stacked within the lane, alternating each marker's vertical offset up or down slightly so adjacent labels don't fight for the same horizontal band. That doubles the lane's required height to roughly 0.8 inches, not because IT is a more important workstream, but because its content is denser in that window.
The two-tier split itself is a small, specific move: take the IT lane's seven milestones sorted by day, assign the odd-numbered ones (1st, 3rd, 5th, 7th) to the upper tier and the even-numbered ones (2nd, 4th, 6th) to the lower tier, each tier's markers sitting on its own horizontal line a few points apart inside the lane — not stacked directly above and below the same x-position, but kept in the same left-to-right day order on each tier. That alternating assignment, not a random scatter, is what keeps the leader lines from crossing once labels get added below each marker.
If a lane's cluster is dense enough that even two tiers would still collide — eight or more milestones inside one 30-day window is where this starts happening on a genuinely IT-heavy carve-out — switch that cluster to small numbered markers on the track and move the full milestone names into a short legend line below the lane, the same density-driven labeling choice that keeps a RACI matrix readable once one role ends up accountable for an unusually long task list. Resist the alternative of shrinking that lane's font size to make seven labels fit where four would have — a lane in 9-point type next to four lanes in 12-point type reads as "this one got crammed in" even to a reader who can't articulate why.
Communication's two milestones, by contrast, need exactly one tier at the minimum height — there's no reason to give it the same 0.8 inches IT needs, and stretching it to match only pushes every lane below it further down the slide for no informational gain.
Select every shape that belongs to one lane — the left-side label textbox, the track background, every marker and its label — and group them with Ctrl+G (or right-click > Group). Rename the group in the Selection Pane to something identifiable, like "Lane_IT_Systems," rather than leaving it as "Group 14." This one habit is what makes the next revision tolerable: when a divestiture-driven deal needs a sixth lane for Carve-Out Separation, you insert one new grouped lane at the right position and run Arrange > Align > Distribute Vertically across the lane groups only — not across every individual shape inside them — and the existing five lanes re-space themselves to make room. Without grouping, that same insert means re-measuring and nudging eleven lanes' worth of shapes (five existing lanes × roughly two shape-clusters each, plus the new one) by hand.
The phase-boundary dashed lines and column headers stay outside any lane group, as a separate background layer, since they span every lane rather than belonging to one — group those together too, so a change to the total day count (someone decides the plan should run to Day 120 instead of Day 100) is one object's width to adjust, not a line redrawn behind every lane individually.
A note from experience: on an integration I worked at a global consulting firm, the 100-day plan went through a redraw almost every steering-committee cycle for a reason that had nothing to do with the underlying plan being unstable — it was that the slide itself couldn't absorb small changes without a full relayout. A workstream lead would move one milestone from Day 42 to Day 55 after a vendor call, and because the lane wasn't grouped and the marker had been placed by eye in the first place, "move one milestone" turned into "re-check whether it still lines up with the phase boundary, then nudge the three markers near it that now look crowded by comparison." Grouping lanes and calculating marker position from the day count doesn't make the underlying integration go any faster — it just stops the slide from generating its own extra work on top of it.
Pull back from the specific lanes and columns above, and the method generalizes into four rules that don't depend on which deal, which workstreams, or which day count is in play:
A private equity portfolio company's first-100-days plan looks different from an M&A integration plan on the surface — different workstream names, often a different phase cadence — but the same four rules hold without modification. A typical PE value-creation 100-day plan swaps the five M&A-style lanes for something like Commercial Excellence, Cost & Procurement, Talent & Leadership, Systems & Data, and Governance & Reporting, and often adds a fourth phase column rather than three, because a sponsor wants a Day 90 board checkpoint ahead of the Day 100 mark — making the split something like 30/30/30/10 rather than 30/30/40.
Nothing about the construction changes. The four columns still get sized to their actual day spans (three equal 30-day columns and one short 10-day one, not four equal quarters), each lane's height still waits for its own milestone count before being fixed, and Governance & Reporting is very often the dense lane on a PE deal — a weekly KPI dashboard cadence, a board-pack template sign-off, and a 13-week cash-flow model all typically start in week one rather than week thirty — where IT was the dense lane on the earlier M&A example. Commercial Excellence, by contrast, often runs lighter in the first 30 days (a pricing audit kickoff, a sales-pipeline data pull) and denser from Day 31 onward once pricing changes and incentive-plan redesigns actually land, which is itself a reminder that "dense in the first phase" isn't a property of a workstream's name — it has to be read off that specific plan's milestone list, same as before. The lane that needs two-tier stacking changes from deal to deal; the decision process for noticing it and sizing around it doesn't.
None of this gets built once and filed away. A 100-day plan slide gets revised at nearly every steering-committee checkpoint — a milestone slips two weeks, a workstream lead adds three items their functional team didn't scope at signing, a sponsor asks to fold two lanes into one after an org redesign — and each of those is exactly the kind of mechanical, rules-based recalculation (recount the lane's milestones, re-check the column proportions, re-run the distribute step) that's tedious precisely because the logic is simple and repetitive, not because it's hard. Advisio, listed on Microsoft AppSource, takes the workstream list and milestone dates and handles that recalculation itself — sizing each lane to its own milestone count and each column to its actual day span as native, editable PowerPoint shapes — so moving a milestone two weeks or adding a sixth lane after a steering committee call is a drag-and-drop edit, not an evening spent re-measuring five lanes that were fine yesterday.