Open Org Workspace

Docs/AI Skills/Roadmap Builder
🗺️

Roadmap Builder

Build a comprehensive people roadmap that balances employee wants with business needs

planning

Who you're working with

Seasoned Chief People Officer. You work with an AI that acts as a seasoned CPO who has navigated the journey from 10 to 5,000+ employees multiple times. It has built dozens of successful people strategies and roadmaps, and is comfortable being data-driven while balancing commercial business needs with what employees actually want.

How it works

1

Share your current thinking

The AI starts by understanding what roadmap items and initiatives you already have in mind, and how you are planning to prioritise them.

What projects or initiatives are on your roadmap for the next 12 months?
How are you planning on prioritising these?
2

Gather inputs

The AI collects the data sources it needs to build a well-informed roadmap. It gathers these one at a time so you are never overwhelmed.

Business strategy, goals, OKRs, and priorities
Engagement or pulse data showing what people want and how they feel
Culture and ways-of-working inputs showing what is healthy and what is not
3

Categorise with Want vs Need

Every roadmap item is cross-referenced against your inputs and scored on two axes. "Need" comes only from business OKRs and goals. "Want" comes only from employee data. No tenuous assumptions are made.

High Want / High Need - high impact for both business and employees
Low Want / High Need - important for business but low employee demand
High Want / Low Need - employees want it but low business priority
Low Want / Low Need - low impact for both
4

Prioritise by quarter

Items are slotted into quarters based on the strength of want and need signals. Each item includes a clear explanation of how it links to business goals.

Which items should be prioritised by quarter?
How does each item link back to business goals?
5

Handle special cases and round off

The AI provides tailored advice for tricky items: co-creation ideas for things employees do not want but the business needs, and communication strategies for things employees want but are not a priority. It also offers to spar on any items you disagree on.

Low Want / High Need: ideas for bringing people along
High Want / Low Need: ideas for communicating why you are not focusing here now
Offer to break down execution tactics for each item
Formatting options (e.g. Notion doc template)

What you'll get

Output

A prioritised people roadmap with quarterly breakdown

Executive summary- High-level overview of the roadmap and its rationale
Quarterly breakdown- Each quarter lists initiatives with Want vs Need category, business link, employee link, and priority level
Want vs Need matrix- Visual categorisation of all items across the four quadrants
Communication recommendations- How to talk about sensitive or surprising prioritisation decisions
Next steps- Execution tactics and formatting options

When to use this

Best for

Building, creating, or designing a people strategy roadmap or HR roadmap

Not for

Product roadmaps, engineering roadmaps, or technical roadmaps - these are outside HR/people scope

Pro tip: use @mentions for richer context

Type @ in the chat to reference additional resources. The AI treats mentioned resources as highest-priority context, giving you much better results.

@
Skills- Type @Roadmap Builder to activate a specific skill workflow
@
Playbooks- Reference a playbook so the AI can draw on its content
@
Your documents- Mention docs you have created in previous chats
@
Openverse content- Reference articles and resources from the knowledge base
@
Newsletters- Include newsletter content as context

How it works:Type @ → browse or search resources → select one → it appears as a chip in your message → the AI receives its full content as priority context.

How the AI behaves

  • Follows a strict conversational flow - gathers your context before generating anything
  • "Need" scoring comes only from business OKRs/goals you provide
  • "Want" scoring comes only from employee data you provide
  • Will not make tenuous assumptions or connect dots that are not there
  • Checks justification for each item before finalising (e.g. will not prioritise ATS if you are not hiring)

Try it

Click to open in chat, or copy the prompt to customise it first.

I need help building a people roadmap for the next 12 months. We are a 200-person Series B SaaS company.

Here are our OKRs and last quarter's engagement survey results. Can you help me prioritise our people team roadmap?

We have 15 potential initiatives and limited bandwidth. Help me figure out what to work on first.

Need more help?

Can't find what you're looking for? Chat directly with the founders.