[{"data":1,"prerenderedAt":240},["ShallowReactive",2],{"writing-article-\u002Fwriting\u002Fthe-quiet-power-of-constraint":3,"writing-index":163},{"id":4,"title":5,"body":6,"cover":148,"coverAlt":148,"date":149,"description":12,"draft":150,"extension":151,"featured":150,"meta":152,"navigation":153,"path":154,"readingTime":155,"seo":156,"stem":157,"summary":158,"tags":159,"__hash__":162},"writing\u002Fwriting\u002Fthe-quiet-power-of-constraint.md","The Quiet Power of a Good Constraint",{"type":7,"value":8,"toc":138},"minimark",[9,13,16,19,24,27,34,40,46,50,53,56,59,62,65,69,72,75,78,82,85,88,91,95,98,104,110,116,122,126,129,132,135],[10,11,12],"p",{},"Ask a team what is blocking them and the answer is often a constraint: not enough engineers, not enough time, an old platform, a regulatory requirement, a brand guideline, a distribution deal.",[10,14,15],{},"Ask the same team to describe their best work and the story usually includes a constraint too. A tight deadline that forced a decision. A small team that made coordination cheap. A platform limit that ruled out the obvious approach and led to a better one.",[10,17,18],{},"The difference is not whether a constraint exists. It is whether the constraint is chosen and understood, or arbitrary and resented.",[20,21,23],"h2",{"id":22},"what-makes-a-constraint-good","What makes a constraint good",[10,25,26],{},"A good constraint has three properties.",[10,28,29,33],{},[30,31,32],"strong",{},"It is real."," It reflects an actual limit (money, time, physics, regulation, attention, trust) rather than a preference dressed up as a rule. Real constraints are worth designing around. Imaginary ones are worth arguing with.",[10,35,36,39],{},[30,37,38],{},"It is legible."," Everyone affected can state it and explain why it exists. A constraint nobody understands becomes folklore, and folklore is hard to revise when the situation changes.",[10,41,42,45],{},[30,43,44],{},"It is binding."," It actually rules something out. A constraint that can be waived whenever the work gets uncomfortable is not a constraint; it is a suggestion with good branding.",[20,47,49],{"id":48},"constraints-as-a-design-tool","Constraints as a design tool",[10,51,52],{},"The most useful constraints narrow the search space in a way that produces better decisions.",[10,54,55],{},"A two-week appetite for a project forces the team to cut scope rather than extend the timeline. That is uncomfortable, and it is the point: it makes the team decide what the smallest valuable version is, rather than assuming that more time equals more value.",[10,57,58],{},"A single-screen limit forces hierarchy. When everything cannot be visible, someone has to decide what matters most. That decision is usually more valuable than the extra screen would have been.",[10,60,61],{},"A “reuse existing infrastructure” rule forces the team to understand the existing system and to distinguish a genuine requirement from a preference for something new. It also keeps operational complexity from growing silently.",[10,63,64],{},"None of these are universal laws. They are constraints chosen for a reason, in a context, and revisited when the reason changes. That is what separates them from neglect.",[20,66,68],{"id":67},"the-difference-between-constraint-and-neglect","The difference between constraint and neglect",[10,70,71],{},"A constraint is chosen and owned. Neglect is what happens when nobody chooses.",[10,73,74],{},"“We can’t hire” can be a constraint or an excuse. If it is a constraint, it comes with a reason (budget, timing, a deliberate choice to invest elsewhere) and a consequence that is being managed. If it is neglect, it is a fact with no owner, used to explain why nothing ambitious happens.",[10,76,77],{},"The test is simple: can the person who owns the constraint explain what it rules out, what it makes possible, and when it would change? If not, it is probably not a constraint yet. It is an unresolved decision.",[20,79,81],{"id":80},"using-constraints-to-test-value","Using constraints to test value",[10,83,84],{},"A useful exercise is to ask what would happen to an idea under a harder constraint. If the value disappears when the team is half the size, or the timeline is halved, or the budget is fixed, that is information about the idea, not just about the resources.",[10,86,87],{},"Ideas that survive constraint tend to be clearer about the problem they solve. They have a core that does not depend on everything going well. Ideas that only work with unlimited resources often turn out to be a collection of adjacent wishes.",[10,89,90],{},"This is not an argument for starving teams. It is an argument for knowing which part of the value is essential and which part is optional.",[20,92,94],{"id":93},"setting-constraints-deliberately","Setting constraints deliberately",[10,96,97],{},"A few practices make constraints useful rather than corrosive.",[10,99,100,103],{},[30,101,102],{},"Name the constraint and its reason."," “We are shipping this in six weeks because the partner integration has a fixed date” is different from “we need it fast”.",[10,105,106,109],{},[30,107,108],{},"Separate the constraint from the solution."," The constraint is the limit; the solution is how you respond to it. Teams often conflate the two and end up defending a particular approach as if it were the limit itself.",[10,111,112,115],{},[30,113,114],{},"Set a review point."," Constraints have a lifespan. A budget limit may change next quarter; a regulatory requirement may not. Write down when the constraint should be revisited so it does not become permanent by accident.",[10,117,118,121],{},[30,119,120],{},"Do not use constraints as a shield."," “We can’t because of X” ends a conversation. “Given X, here are the options” starts one.",[20,123,125],{"id":124},"the-strategic-version","The strategic version",[10,127,128],{},"At a higher level, strategy is partly the art of choosing which constraints to accept and which to fight.",[10,130,131],{},"Accepting a constraint can be a deliberate move: staying in one market, refusing a certain customer segment, keeping the product small, avoiding a platform dependency. Fighting a constraint can be equally deliberate: investing in infrastructure because the current limit will cap the next three years.",[10,133,134],{},"The failure mode is neither. It is drifting: accepting constraints that should be challenged and challenging constraints that are actually the source of the advantage.",[10,136,137],{},"A good constraint is not the enemy of good product work. It is often the thing that makes it possible.",{"title":139,"searchDepth":140,"depth":140,"links":141},"",2,[142,143,144,145,146,147],{"id":22,"depth":140,"text":23},{"id":48,"depth":140,"text":49},{"id":67,"depth":140,"text":68},{"id":80,"depth":140,"text":81},{"id":93,"depth":140,"text":94},{"id":124,"depth":140,"text":125},null,"2026-02-10",false,"md",{},true,"\u002Fwriting\u002Fthe-quiet-power-of-constraint",4,{"title":5,"description":12},"writing\u002Fthe-quiet-power-of-constraint","Constraints are usually treated as obstacles. A good one narrows the search space, forces a real choice, and makes the work more honest.",[160,161],"product-thinking","product-strategy","_8HFpUbeJd7TCgu28UTMMq6wEaHeX6J8JEJU_cB1E_A",[164,171,179,186,192,198,204,212,214,221,227,234],{"path":165,"title":166,"summary":167,"date":168,"tags":169,"featured":153,"readingTime":155},"\u002Fwriting\u002Fwhat-ai-changes-about-product-work","What AI Changes About Product Work, and What It Doesn’t","The cost of producing a prototype, a spec or a synthesis has collapsed. The cost of knowing what is worth building has not. That gap is where product judgement now lives.","2026-11-04",[170,160],"ai",{"path":172,"title":173,"summary":174,"date":175,"tags":176,"featured":150,"readingTime":178},"\u002Fwriting\u002Froadmaps-are-arguments","Roadmaps Are Arguments, Not Schedules","A roadmap is a set of claims about why these problems, in this order, with these trade-offs. When it becomes a delivery calendar, the reasoning disappears and the promises take over.","2026-10-14",[161,177],"decision-making",3,{"path":180,"title":181,"summary":182,"date":183,"tags":184,"featured":150,"readingTime":155},"\u002Fwriting\u002Fdiscovery-is-a-budget","Discovery Is a Budget, Not a Phase","Treating discovery as a stage before delivery assumes uncertainty is front-loaded. It isn’t. Discovery works better as a recurring spend that every cycle pays into.","2026-09-23",[185,161],"discovery",{"path":187,"title":188,"summary":189,"date":190,"tags":191,"featured":150,"readingTime":155},"\u002Fwriting\u002Fcost-of-a-decision-you-didnt-make","The Cost of a Decision You Didn’t Make","Deferred decisions feel safe because nothing visible happens. But indecision charges interest, in rework, lost context, and options that quietly expire.","2026-08-19",[177,160],{"path":193,"title":194,"summary":195,"date":196,"tags":197,"featured":150,"readingTime":178},"\u002Fwriting\u002Fthe-feature-was-never-the-problem","The Feature Was Never the Problem","A feature request is a compressed problem statement with the reasoning removed. If you ship the request without unpacking it, you often solve the smallest part of the problem.","2026-06-30",[160,185],{"path":199,"title":200,"summary":201,"date":202,"tags":203,"featured":150,"readingTime":178},"\u002Fwriting\u002Fprioritisation-is-about-evidence","Prioritisation Is a Story About Evidence","Frameworks like RICE do not make decisions. They make assumptions comparable. The quality of a prioritisation is the quality of the evidence and the honesty about what gets displaced.","2026-05-12",[161,177],{"path":205,"title":206,"summary":207,"date":208,"tags":209,"featured":150,"readingTime":155},"\u002Fwriting\u002Fstakeholders-are-not-obstacles","Stakeholders Are Not Obstacles","“Stakeholder management” often frames other people as friction. But they hold information the product team lacks. Treat them as co-owners of the constraint, not gatekeepers.","2026-03-24",[210,211],"practice","leadership",{"path":154,"title":5,"summary":158,"date":149,"tags":213,"featured":150,"readingTime":155},[160,161],{"path":215,"title":216,"summary":217,"date":218,"tags":219,"featured":150,"readingTime":155},"\u002Fwriting\u002Fwhen-research-stops-being-useful","When Research Stops Being Useful","Research becomes decorative when it is disconnected from a decision. More interviews will not fix a team that has not agreed on what it is trying to learn.","2025-12-02",[220,185],"research",{"path":222,"title":223,"summary":224,"date":225,"tags":226,"featured":150,"readingTime":155},"\u002Fwriting\u002Fthe-product-review","The Product Review That Actually Changes the Product","Most product reviews are status meetings with slides. A useful one changes a decision, and that requires a different format, a different question set and a named owner.","2025-10-21",[210,177],{"path":228,"title":229,"summary":230,"date":231,"tags":232,"featured":150,"readingTime":178},"\u002Fwriting\u002Ftools-dont-make-the-product","Tools Don’t Make the Product","A new tool cannot fix an undefined workflow. It usually makes the disagreement faster, more visible and more expensive.","2025-09-09",[233,210],"tools",{"path":235,"title":236,"summary":237,"date":238,"tags":239,"featured":150,"readingTime":155},"\u002Fwriting\u002Foutcomes-are-a-habit","Outcomes Are a Habit, Not a Metric","Teams say they are outcome-driven but manage by output because output is legible. Outcomes require a cadence of looking at behaviour and the discipline to change course.","2025-07-15",[161,210],1795010564317]