Roadmap · Milestone
Roadmap & Milestone
What Is a Roadmap?
- A big-picture plan of phases on a timeline
- Define milestones as states, not durations
- Mark items as confirmed, planned, or under review
Once you start drawing a roadmap, the questions asked in meetings change. Until then, each team asks the others, “When will that be done?” Once a one-page picture is on the table, the question shifts to “So what do we push back?” That is because the fact that resources are finite becomes visible on the page. When the item marketing wants in Q3 and the item engineering is already committed to in Q3 land in the same cell, the priority fight stops being a contest of volume and becomes a sequencing negotiation.
There are two main formats. The time-based format, with quarters or half-years on the axis, suits IT services and manufacturing, where delivery dates are bound by contract. The theme-based format, with just three columns, “Now / Next / Later,” suits service and platform teams whose priorities shift often. For milestones, 4–6 per six-month initiative, spaced 2–3 weeks apart, is easy to manage. It is easy to confuse with a Gantt chart, but a Gantt chart is made of bars that span a period, while a milestone is a point event with zero effort. The moment you write “two weeks of development” in a milestone cell, it becomes a work item, not a decision point.
The most common failure happens the moment a milestone is reported as a percentage of progress. “Development 80% complete” is a feeling, not a verdict, and that 80% will still read 80% two months later. Unless the verdict passes from the team that built the deliverable to the team that receives and uses it in the next stage, the pass criteria get more lenient every time. Another trap: when sales copies the “under review” column of the roadmap straight into a customer proposal, an internal plan turns into an external commitment. At that point a delay becomes a breach-of-contract problem, so it is safer to build a separate version for external sharing that keeps only the confirmed phases.
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum Consulting
Ara LimSpecialist in global leadership, AI, and business communicationIt took hold in corporate practice through Motorola's technology roadmapping in the 1970s, and later expanded into product and strategy roadmaps.
Consider a hypothetical case. Company A, an auto parts manufacturer (1,200 employees, KRW 380 billion (≈ US$284,303,500) in annual revenue), decided to build a new leadership training program for newly appointed team leaders within 12 months. Four months after kickoff, the HR team was still reporting only “design in progress,” and the CEO kept asking in every meeting, “So what percent is done?”
- The head of planning put it bluntly: “If this overlaps with the ERP replacement, the business units won’t show up for training.” So they fixed the final goal as “all 80 new team leaders complete the program by January next year” and worked backward from there.
- They split the 12 months into four phases and kept only six milestones. Each was written as a sentence you can mark done or not done, such as “End of June: two pilots with 12 team leaders completed, satisfaction of 4.0/5.0 or higher.”
- They handed the review to three production-division team leaders who would attend the program, not to the HR team. The first review rejected the draft because “the cases are not about our factory,” and the schedule slipped by three weeks.
- They used three markings on the roadmap: confirmed (black), planned (gray), and under review (dotted). Overseas subsidiary rollout, which had no budget yet, was drawn as dotted. When the Vietnam subsidiary head asked, they could answer, 'That is still in the dotted zone.'
- They ran a 30-minute update meeting on the first Tuesday of every month and left the change history right under the diagram. At the third meeting, a delay in the content developer's contract came to light, and they brought in a replacement vendor within two weeks.
- The final completion came three weeks behind target, in the third week of January, but 76 of the 80 target participants completed the program, and the question “What percent is done?”, which had recurred for four months, disappeared from meeting minutes after June.