> [!tldr] pulling together commonly recommended ideas [[Design Thinking Framework]] Prescribes an approach that's not terribly out of line with the [[TOGAF|Architecture Development Method]]. I thought I had a third example, but maybe not. [[Persuasive Conversation Template]]s, maybe? Overlaps: - [[Selling Why, not What|start with why]] - before you start with your customer (if you have one), figure out what you want to get out of the project. - When you meet with the customer, also [[Selling Why, not What|start with why]]. - You're on their team. Think in their terms and [[Solving People’s Problems Requires Understanding Their Incentives]]. Use their language, [[Avoid Jargon]]. - When you hear the problem, ask how they know it's a problem and what they truly want to do. Make sure it's not a case of [[The XY Problem]]. Get to a discrete example you can target or use to elicit other issues. - Repeat their problems and goals in simple terms and confirm until you get [["That's Right" - Your Negotiation Goal|that's right]]. - Scope what can realistically be accomplished. - It's better to fully solve 1/3rd of the problem than it is to 1/3rd solve all the problems. - ☝️ Only if your [[What is a Strategy|strategy]] is known and the solutions you produce on parts will add to the whole. - "[[We won't be able to do everything, but what we do we'll do well.]]" - Confirm the scope and selection you've made is valuable with the stakeholders. The [[Fist of Five]] is a good approach. - Seek to understand the situation at hand - look for high-level **** # More ## Source -