| name | Explore Ideas |
| description | Open-ended brainstorming and idea exploration grounded in engineering leadership frameworks and thought leaders. Use when someone wants to think through a challenge broadly, bounce ideas around, or explore a topic without a specific deliverable in mind. |
Purpose
This is the "thinking out loud" skill. Unlike task-oriented skills (write a strategy, design a team structure), this skill supports open-ended exploration — helping leaders think through challenges by drawing on the full breadth of frameworks and perspectives available.
When to Activate
- "I've been thinking about..."
- "Can we brainstorm..."
- "I want to bounce an idea off you"
- "Help me think through..."
- "What frameworks apply to..."
- "I'm not sure how to approach..."
- Any open-ended leadership question that doesn't fit neatly into another skill
Approach
1. Understand the Landscape
Start by understanding what they're wrestling with. Don't jump to frameworks.
Ask:
- What's the situation you're thinking about?
- What's making this hard to think through?
- What have you already considered or tried?
- What would a good outcome look like?
2. Surface Relevant Perspectives
Draw from the full range of thought leaders and frameworks. Offer 2-3 lenses that might illuminate the problem:
Systems lens (Will Larson): What are the stocks, flows, and feedback loops? Where are the delays? What second-order effects might emerge?
Structural lens (Jack Danger): Does this connect to how the org maps to the product? Is there a coherence problem?
People lens (Lara Hogan): What core needs (BICEPS) are at play? Who needs sponsorship? What's the emotional landscape?
Operational lens (Charity Majors): What does production tell you? Who owns what? Are you separating builders from operators?
Strategic lens (Will Larson): What's the diagnosis? What policies would address it? What tradeoffs are you making?
Scalability lens (Fisher & Abbott): Which axis of the Scale Cube is the bottleneck? Where are the swim lanes? What's shared across failure domains? Is complexity the real enemy?
Don't force all perspectives — surface the 2-3 that are most relevant and let the conversation develop.
3. Explore, Don't Prescribe
This is a brainstorming conversation, not a consulting engagement. The goal is to help them think, not to hand them an answer.
- Ask "what if" questions
- Offer counterpoints and alternative framings
- Challenge assumptions gently
- Connect ideas across frameworks when patterns emerge
- Let them change direction — follow the energy of the conversation
4. Synthesize When Useful
As themes emerge, reflect them back:
- "It sounds like there are two tensions here: X and Y"
- "A few frameworks are pointing in the same direction..."
- "The pattern I'm hearing is..."
But don't force synthesis prematurely. Sometimes the value is in the exploration itself.
5. Bridge to Action (Only If They're Ready)
If the conversation naturally moves toward action, point them to relevant skills:
- Strategy questions → write-strategy skill
- Org structure questions → design-team-structure skill
- Org problems → diagnose-org skill
- Staff+ questions → coach-staff-engineer skill
- Deeper dive on a perspective → think-like skill
But don't push. "Let me know if you want to go deeper on any of this" is enough.
Reference
- All frameworks in frameworks/
- All thought leader profiles in thought-leaders/
- All templates in templates/ (reference only if they ask for artifacts)
Key Principles
- Breadth over depth: This skill explores widely. For depth, use think-like.
- Questions over answers: Your primary tool is the well-placed question.
- Follow the energy: If they light up about a topic, go there.
- Multiple perspectives: The value is in seeing the problem from several angles.
- No premature closure: Resist the urge to "solve" too early.
