pull-framework

## The 4 Questions Ask each in order. Don't prescribe solutions until all four are answered. ### P — Project "What are you working on?" Get the full picture. Not just the task, but the context. What's the project? What's the goal? Who's involved? What stage is it at? If the user jumps to a narrow problem, zoom out first: "Before we dig into that — what's the bigger thing this is part of?" ### U — Urgent "What's urgent about it?" Why now? What's the deadline? What breaks if this doesn't get resolved? Is the urgency real (external deadline, user impact) or perceived (internal pressure, perfectionism)? If nothing is urgent, that's useful information. It means there's time to think properly instead of reacting. ### L — List "What have you tried?" Everything attempted so far. What worked partially? What failed completely? What did you learn from each attempt? CRITICAL: People often skip what they've already tried and go straight to "help me solve this." Pull it out. Prior attempts contain signal about what the real problem is. ### L — Limitations "What's not working? What constraints are you operating under?" What's blocking progress? Resource constraints? Technical limitations? Organizational politics? Knowledge gaps? Separate constraints you can change from constraints you must accept. The strategy looks different for each. ## After PULL Only after all four questions are answered, synthesize: 1. **Restate the situation** in your own words. Let the user correct you. 2. **Identify the actual problem** (which may be different from what the user initially described). 3. **Propose a direction** — not a full solution, but a next step. ## Output ```markdown # Discovery Brief: [Topic] Date: [date] ## Project [What they're working on, in context] ## Urgency [Why now, real vs. perceived] ## Prior Attempts [What's been tried, what was learned] ## Limitations [Changeable vs. fixed constraints] ## Actual Problem [Restated after discovery — may differ from initial framing] ## Recommended Next Step [One specific action] ``` Based on the PULL Framework. Understand before prescribing. ## Next step Problem discovered → run **problem-framing** to diagnose deeper, or **preflight** if you're ready to scope a session. --- Part of the [ThinkHaven Method Kit](https://github.com/hollandkevint/thinkhaven-method-kit) by Kevin Holland. Full Board of Directors experience: [ThinkHaven](https://thinkhaven.co/try)