technical-roadmaps
This skill helps teams develop structured technical roadmaps by applying the Rumelt framework (diagnosis, guiding policies, actions) and emphasizing written documentation and conservative tool choices. Use it when planning engineering priorities, managing technical debt, designing system architecture, or ensuring technical decisions align with product and business goals rather than pursuing novel technologies.
git clone --depth 1 https://github.com/RefoundAI/lenny-skills /tmp/technical-roadmaps && cp -r /tmp/technical-roadmaps/skills/technical-roadmaps ~/.claude/skills/technical-roadmapsSKILL.md
# Technical Roadmaps Help the user create effective technical roadmaps using frameworks and insights from 1 product leader. ## How to Help When the user asks for help with technical roadmaps: 1. **Understand the context** - Ask about their current technical state, team size, and business constraints 2. **Ensure it's written down** - A strategy that isn't documented can't be debugged or aligned around 3. **Apply the Rumelt framework** - Structure as Diagnosis (what's the problem), Guiding Policies (principles for decisions), and Actions (what you'll do) 4. **Favor boring strategies** - Help them resist the urge to introduce new tools when existing ones would suffice ## Core Principles ### Write it down Will Larson: "The first rule of strategy is that if you write it down, then you can improve it. If it's not written down, it's hard to say if this PM is just not a good PM or if they're trying to apply a strategy they've misunderstood." A written strategy provides a baseline that can be critiqued and improved. ### Boring strategies often win Will Larson: "A common strategy that's really good but very boring is we only use the tools we have today. Engineers want to introduce new programming languages, new databases, new cloud providers. A really good strategy for almost all companies is we just use the standard kit we already have." Focus engineering energy on business-valued problems rather than technical novelty. ### Use the Rumelt framework Structure technical strategy using Richard Rumelt's framework: Diagnosis (what's the core challenge?), Guiding Policies (what principles will guide decisions?), and Actions (what specific things will you do?). ### Create a standard kit Define a list of approved tools, languages, and platforms. This limits technical sprawl and allows teams to focus on solving core product problems rather than reinventing infrastructure. ## Questions to Help Users - "Is this technical strategy written down somewhere that anyone can reference?" - "What is the core technical challenge you're trying to solve (the diagnosis)?" - "What principles will guide your technical decisions (the guiding policies)?" - "Are you adding new tools because you need them, or because they're interesting?" - "What does your 'standard kit' of approved technologies look like?" - "How does this technical roadmap connect to business outcomes?" ## Common Mistakes to Flag - **Unwritten strategy** - A strategy that only exists in someone's head can't be debugged or aligned around - **Tool proliferation** - Introducing new technologies when existing ones would work creates maintenance burden - **No connection to business value** - Technical roadmaps that don't tie to product or business outcomes lack justification - **All diagnosis, no action** - Good strategy requires specific actions, not just analysis of the problem - **Missing guiding policies** - Without principles, every technical decision becomes a debate from scratch ## Deep Dive For all 2 insights from 1 guest, see `references/guest-insights.md` ## Related Skills - Managing Tech Debt - Platform Strategy - Engineering Culture - Prioritizing Roadmap
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.