{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib3265hnxfvtt4llhettnql2d6ziz6ffpetge2vvyhryan7zicwg4",
    "uri": "at://did:plc:zw76zx26b4myxtkhzczd3q7x/app.bsky.feed.post/3mg5ptkp74i42"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreigdgkxqbg6vwkjged354qf2mg5i4onulxh66i5j2tt2u3hnmqjcuu"
    },
    "mimeType": "image/jpeg",
    "size": 482864
  },
  "description": "Agile? Waterfall? Hybrid? None of them fit your messy reality perfectly. And that's okay.\n\nLet me guess:\n\nYou've been asked (probably more than once): \"So, are you Agile or Waterfall?\"\n\nAnd you've probably said something like, \"We're Agile... mostly. With some Waterfall elements. It's hybrid. Kind of.\"\n\nThen comes the awkward silence where the other person either nods politely or launches into why their methodology is superior.\n\nHere's what nobody wants to admit:\n\nNone of the methodologies fit p",
  "path": "/the-methodology-trap-and-how-to-escape-it/",
  "publishedAt": "2026-03-03T12:00:23.000Z",
  "site": "https://www.getintentional.net",
  "textContent": "Agile? Waterfall? Hybrid? None of them fit your messy reality perfectly. And that's okay.\n\n* * *\n\nLet me guess:\n\nYou've been asked (probably more than once): **\"So, are you Agile or Waterfall?\"**\n\nAnd you've probably said something like, \"We're Agile... mostly. With some Waterfall elements. It's hybrid. Kind of.\"\n\nThen comes the awkward silence where the other person either nods politely or launches into why  _their_ methodology is superior.\n\nHere's what nobody wants to admit:\n\n**None of the methodologies fit perfectly.**\n\nNot Agile. Not Waterfall. Not SAFe. Not Scrum. Not Kanban.\n\nWhy? Because methodologies are designed for  _ideal_ scenarios. And your project? It's beautifully, frustratingly, uniquely messy.\n\nSo you have a choice:\n\nYou can keep trying to force your square-peg project into a round-hole methodology.\n\nOr you can become a **bespoke tailor**.\n\n* * *\n\n### **The Principle: Adaptive Thinking**\n\nAdaptive Thinking means customizing your approach to fit the unique context of each project rather than rigidly following a single methodology.\n\nIt's about being flexible, not flaky. Intentional, not inconsistent.\n\nThink about it:\n\nWould you run a 3-month website redesign the same way you'd run a 2-year enterprise software implementation?\n\nWould you manage a team of 5 co-located developers the same way you'd manage a distributed team of 50 across 6 time zones?\n\nWould you approach a project with clear requirements the same way you'd approach one where stakeholders \"will know it when they see it\"?\n\nOf course not.\n\n**Context matters.** And leaders who adapt to context deliver better results than those who follow a playbook.\n\n* * *\n\n### **The Methodologist Trap**\n\nI see this all the time:\n\nA PM gets certified in Agile (or PMP, or Scrum, or whatever). They learn the framework. They internalize the rules. And then they become... rigid.\n\nThey quote the methodology like scripture:\n\n  * \"That's not Agile\"\n  * \"We can't do that in Waterfall\"\n  * \"The framework says we need a daily standup\"\n\n\n\nAnd meanwhile, the project is struggling because  _the methodology isn't serving the work._\n\nHere's the truth: **Methodologies are tools, not identities.**\n\nYou're not an \"Agile PM\" or a \"Waterfall PM.\"\n\nYou're a project leader who uses whatever approach serves the project best.\n\nSometimes that's Agile sprints. Sometimes it's a detailed Gantt chart. Sometimes it's a hybrid nobody's invented yet.\n\nAnd that's not failure. That's leadership.\n\n* * *\n\n### **Tailoring, Not Compromise**\n\nLet me be clear: Adaptive Thinking isn't about doing whatever you feel like or abandoning structure.\n\nIt's about **intentional customization**.\n\nAsk yourself:\n\n  * What does  _this_ project need to succeed?\n  * What does  _this_ team need to thrive?\n  * What do  _these_ stakeholders need to stay confident?\n  * What constraints am I working within (time, budget, resources, culture)?\n\n\n\nYour answers should drive your approach.\n\nMaybe you need:\n\n  * Agile sprints for development + Waterfall gates for compliance\n  * Daily standups for the core team + weekly syncs for extended stakeholders\n  * Flexible scope in some areas + locked requirements in others\n\n\n\nThat's not \"hybrid\" because you couldn't pick a side.\n\nThat's **bespoke** because you designed it to fit.\n\n* * *\n\n### **Change Isn't the Enemy**\n\nHere's the other part of Adaptive Thinking: **embracing change as opportunity, not disruption.**\n\nMethodologists hate change. It breaks their process. It messes up their plan. It requires... adaptation.\n\nBut leaders? Leaders expect change.\n\nThey know:\n\n  * Stakeholder priorities will shift\n  * New information will emerge\n  * Market conditions will evolve\n  * Teams will grow and change\n\n\n\nAnd instead of resisting that reality, they build flexibility into how they work.\n\nThey create space for adaptation without chaos.\n\n* * *\n\n### **The AI Advantage**\n\nThis is where GenAI becomes incredibly powerful:\n\nAI can help you **rapidly customize frameworks and processes** to fit your specific context without starting from scratch every time.\n\nNeed a retrospective format for a remote team with trust issues? AI can design it.\n\nNeed a decision framework that balances speed with stakeholder input? AI can build it.\n\nNeed to adapt your sprint structure for a team juggling maintenance work and new features? AI can map it out.\n\nYou bring the context. AI helps you tailor the approach.\n\nAnd instead of spending hours Googling \"hybrid Agile-Waterfall templates,\" you spend 10 minutes crafting a custom process that actually fits your reality.\n\n* * *\n\n### **This Week's Prompt**\n\nUse this prompt to design a custom approach for your current project:\n\n**Copy/paste this into ChatGPT or Claude:**\n\n\n    WHO: Act as an expert project methodology designer with experience across Agile, Waterfall, Lean, and hybrid approaches\n\n    WHY: because my current project doesn't fit neatly into any standard methodology, and I need a tailored approach that serves my specific context\n\n    WHAT: based on the project details below, design a customized project framework that addresses my unique constraints and needs. Include:\n    1. Recommended project phases or iterations\n    2. Key ceremonies or checkpoints\n    3. Decision-making approach\n    4. Flexibility points where adaptation is expected\n\n    HOW: outline a clear framework with 4-6 key elements, explain WHY each element fits my context (not just what to do), and identify where I should stay structured vs. where I should remain flexible\n\n    [Paste your project context: team size/structure, timeline, stakeholder landscape, requirements clarity, constraints, risks, etc.]\n\n\n**What you'll get:** A custom methodology designed for your reality: not someone else's ideal scenario.\n\n* * *\n\n### **This Week's Challenge**\n\nLook at how you're currently running your project and ask yourself:\n\n**\"Am I doing this because it serves the project, or because it's 'the way we do things'?\"**\n\nFind ONE process, meeting, or artifact that doesn't fit your context and adapt it.\n\nMaybe it's:\n\n  * Shortening standups because your team works asynchronously\n  * Adding a visual board because stakeholders need to \"see\" progress\n  * Dropping a ceremony that's become a checkbox exercise\n  * Creating a custom review format that actually generates useful feedback\n\n\n\nYou're not abandoning structure. You're not \"going rogue.\"\n\n**You're leading with Adaptive Thinking.**\n\nYou're tailoring your approach to serve the work.\n\nAnd when you do that—when you stop being a methodologist and start being a bespoke tailor—your projects run smoother, your teams perform better, and your stakeholders trust you more.\n\nBecause you're not following a script.\n\nYou're leading with intention.\n\n* * *\n\nGet Intentional,\n\n\nPaul\n\n**P.S.** The best project leaders I know can't be put in a box. They're certified in multiple methodologies, but they don't worship any of them. They adapt. If you're still trying to \"pick a side,\" give yourself permission to stop. Your job isn't to be Agile or Waterfall. Your job is to deliver value. Use whatever helps you do that.\n\n* * *\n\n##",
  "title": "The methodology trap (and how to escape it)",
  "updatedAt": "2026-03-03T12:00:23.634Z"
}