# Entrowise > Problem-Centric Coaching for Technology Leaders using the PPA Method (Problem → Principle → Action) Entrowise helps technology and delivery leaders stop firefighting recurring delivery problems and start solving them at their root. Founded by Gourab Nanda. Contact: gourab@entrowise.com | (800) 909-3738 | https://entrowise.com --- ## Services - **AI Coaching Agent (Beta)**: OpenAI Assistants-powered diagnostic tool applying the PPA Method to technology delivery problems. https://entrowise.com/AI-diagnostic-coaching-tool - **Leadership Coaching Workshops**: Multi-week cohort programs for Engineering Managers, Delivery Leads, Scrum Masters, Product Leaders, and Technology Leaders. https://entrowise.com/leadership-coaching-workshops - **Enterprise Problem-Centric Coaching**: Deep organizational coaching, custom AI Coaching Agent development, and leadership training for organizations with 100+ engineers. https://entrowise.com/enterprise-consulting - **Principles Library**: 34 delivery principles across 6 categories for diagnosing recurring delivery problems. https://entrowise.com/principles - **PPA Method**: Full explanation of the Problem → Principle → Action coaching framework. https://entrowise.com/ppa-method - **Blog**: Practical articles on software delivery constraints, technology leadership, and applying the PPA Method. https://entrowise.com/blog --- ## The PPA Method (Problem → Principle → Action) The PPA Method is a structured coaching framework for diagnosing and solving complex delivery problems in technology organizations. **Problem phase**: Deeply understand the system behavior creating the issue — not just symptoms, but root causes and system dynamics. Identify what the system is optimizing for and why it produces these outcomes. Frame the problem at the system level, not the person level. **Principle phase**: Identify which fundamental delivery principles are being violated or under-applied. Map violated principles from the knowledge base. Understand why problems keep recurring despite process investments. **Action phase**: Take targeted, principle-aligned actions that are safe-to-try within existing constraints. Actions should reinforce healthy system behavior and address root causes, not symptoms. The PPA Method addresses recurring problems that persist despite Agile, DevOps, and AI tooling investments: misalignment, delivery delays, technical debt, accountability gaps. --- ## Principles Library — All 34 Principles ### Lean Principles **1. Optimize the Whole** URL: https://entrowise.com/principles/optimize-the-whole Optimize the end-to-end value delivery system rather than individual teams or components. System performance is determined by flow across the whole, not by local efficiency. Teams meeting local goals while overall delivery remains slow or unpredictable is a sign this principle is violated. **2. Build Quality In** URL: https://entrowise.com/principles/build-quality-in Treat quality as a built-in system property rather than an inspection step at the end. Preventing defects at the source is always faster and cheaper than detecting and fixing them later. Quality gates at the end of the process, large regression cycles, and rework loops signal this principle is violated. **3. Eliminate Waste** URL: https://entrowise.com/principles/eliminate-waste Continuously identify and remove activities that consume resources without adding customer value. Waste slows delivery, obscures real problems, and diverts energy from what matters. Waste types include: unnecessary hand-offs, waiting, over-processing, defects, and unused features. **4. Deliver Value Fast (Reduce Lead Time)** URL: https://entrowise.com/principles/deliver-value-fast Reduce the time between recognizing a need and delivering value to the customer. Fast delivery enables faster learning, earlier feedback, and greater responsiveness to change. Long queues, batch releases, and slow feedback cycles indicate this principle is violated. **5. Defer Commitment (Last Responsible Moment)** URL: https://entrowise.com/principles/defer-commitment Delay irreversible decisions until the last responsible moment — when the most information is available and the cost of change is still acceptable. Premature lock-in, big upfront design, and speculative work indicate this principle is violated. **6. Continuous Improvement (Kaizen)** URL: https://entrowise.com/principles/continuous-improvement Build a culture of ongoing, incremental improvement where everyone contributes to making the system better. Improvement should be habitual, not episodic. Retrospectives that produce no lasting change signal this principle is violated. **7. Respect People** URL: https://entrowise.com/principles/respect-people Design systems that respect the expertise, judgment, and dignity of the people who do the work. People are not resources — they are the intelligence of the system. Micromanagement, blame cultures, and ignoring worker insights signal this principle is violated. ### Agile Principles **8. Embrace Change** URL: https://entrowise.com/principles/embrace-change Adapt plans and priorities based on learning and emerging realities. In complex systems, change is evidence of learning — not a failure of planning. Rigid change control processes and punishing scope changes signal this principle is violated. **9. Empowered, Cross-Functional Teams** URL: https://entrowise.com/principles/empowered-cross-functional-teams Design teams with the skills, authority, and context required to deliver end-to-end value. Empowered, cross-functional teams reduce dependencies, speed decisions, and improve ownership. Frequent escalations and cross-team waiting signal this principle is violated. **10. Frequent Feedback Loops** URL: https://entrowise.com/principles/frequent-feedback-loops Create frequent, meaningful feedback loops that inform decisions and guide adaptation. Feedback is how learning enters the system and influences behavior. Infrequent demos, delayed retrospectives, and slow customer feedback signal this principle is violated. **11. Incremental Delivery** URL: https://entrowise.com/principles/incremental-delivery Deliver value in small, meaningful increments to reduce uncertainty and enable learning. Incremental delivery exists to discover the right solution when outcomes cannot be known upfront. Large releases, long delivery cycles, and "big bang" launches signal this principle is violated. **12. Transparency** URL: https://entrowise.com/principles/transparency Make work, risks, progress, and outcomes visible so decisions are grounded in shared reality. Transparency enables informed action; without it, decisions are based on assumptions and perception. Hidden backlogs, optimistic status reports, and surprise delays signal this principle is violated. **13. Value Is Contextual and Time-Dependent** URL: https://entrowise.com/principles/value-is-contextual-and-time-dependent Recognize that value is not fixed. It evolves based on timing, context, and changing conditions. Decisions about what is valuable must be continuously revisited. Building features for last year's strategy and treating the backlog as permanent signal this principle is violated. ### System Integrity Principles **14. Accountability Must Match Control** URL: https://entrowise.com/principles/accountability-must-match-control People and teams can only be accountable for outcomes they have the authority, capability, and resources to influence. Accountability without control breeds frustration and learned helplessness. Holding teams accountable for outcomes they cannot influence signals this principle is violated. **15. Alignment over Compliance** URL: https://entrowise.com/principles/alignment-over-compliance Sustainable delivery improvement comes from shared understanding and genuine commitment — not from enforced process adherence. When people understand why, they adapt intelligently. Teams following the letter but not the spirit of processes signals this principle is violated. **16. Constraints Create Focus** URL: https://entrowise.com/principles/constraints-create-focus Constraints are not just limitations — they are design forces that create boundaries, focus energy, and guide decisions. Effective leaders work with constraints, not around them. Unlimited scope, unlimited WIP, and unlimited team size signal this principle is violated. **17. Learning Before Scaling** URL: https://entrowise.com/principles/learning-before-scaling Validate that a practice, solution, or system works at small scale before expanding it. Scaling unvalidated approaches amplifies both costs and failure modes. Rolling out new processes organization-wide without piloting first signals this principle is violated. **18. Every Hand-Off Has a Cost** URL: https://entrowise.com/principles/every-hand-off-has-a-cost Every time work moves between people, teams, or systems, information is lost, delay accumulates, and accountability becomes diffuse. Design flows that minimize unnecessary hand-offs. Multiple team dependencies per feature and long approval chains signal this principle is violated. **19. More Choices Make Decision-Making Harder** URL: https://entrowise.com/principles/more-choices-make-decision-making-harder Expanding options increases cognitive load and often leads to worse decisions, analysis paralysis, and delayed action. Clarity and constraints often serve better than freedom and abundance. Endless prioritization debates and inability to commit signal this principle is violated. **20. New Solutions Create New System Constraints** URL: https://entrowise.com/principles/new-solutions-create-new-system-constraints Every solution introduces new dependencies, trade-offs, and constraints. Leaders must anticipate second-order effects — what new problems will this solution create? Tool proliferation, process bloat, and unintended consequences signal this principle is violated. **21. Understand the Original Intent Before Removing or Replacing Existing Capabilities** URL: https://entrowise.com/principles/understand-original-intent-before-removing Before removing or replacing an existing process, rule, or system, first understand why it was introduced. Removing constraints without understanding their purpose often reintroduces the original problem. **22. Vague Guidance Creates False Alignment** URL: https://entrowise.com/principles/vague-guidance-creates-false-alignment Ambiguous goals, principles, or strategies create the illusion of agreement while allowing divergent interpretations. False alignment is more dangerous than open disagreement. Teams pursuing different interpretations of the same goal signals this principle is violated. ### Scrum Principles **23. Empiricism** URL: https://entrowise.com/principles/empiricism Base decisions on observation, experimentation, and evidence rather than assumptions, predictions, or plans. In complex environments, what is true must be discovered, not assumed. Detailed long-range plans treated as commitments and ignoring sprint data signal this principle is violated. **24. Timeboxed Learning Cycles** URL: https://entrowise.com/principles/timeboxed-learning-cycles Use fixed-length cycles to create predictable cadences for planning, execution, inspection, and adaptation. Timeboxes create urgency, limit scope creep, and force regular reflection. Sprints with no real review or retrospective and constantly extending sprint timelines signal this principle is violated. **25. Commitment to Outcome Intent** URL: https://entrowise.com/principles/commitment-to-outcome-intent Commit to the intent and outcome of a goal — not to a fixed scope of deliverables. Rigid scope commitments in complex work prevent the adaptation needed to actually achieve the goal. Teams treating sprint commitments as fixed contracts signal this principle is violated. ### AI & Automation Principles **26. Human Accountability Cannot Be Delegated** URL: https://entrowise.com/principles/human-accountability-cannot-be-delegated Humans retain accountability for decisions and outcomes even when AI systems perform the work. Delegation of tasks does not transfer responsibility for results. "The AI decided it" as an excuse for poor outcomes signals this principle is violated. **27. Decision Authority Must Be Explicit** URL: https://entrowise.com/principles/decision-authority-must-be-explicit In systems where AI and humans collaborate, it must be unambiguous who — or what — has authority to make each category of decision. Unclear authority leads to gaps, conflicts, and unintended outcomes. **28. Observability Before Autonomy** URL: https://entrowise.com/principles/observability-before-autonomy Before granting AI systems autonomous action, ensure humans can observe what the system is doing, why, and what outcomes it is producing. You cannot govern what you cannot see. **29. Feedback Loops Must Include AI Behavior** URL: https://entrowise.com/principles/feedback-loops-must-include-ai-behavior Feedback and review mechanisms must explicitly include evaluation of AI agent behavior — not just human team behavior. AI systems can drift, degrade, or amplify errors silently. ### Flow & Kanban Principles **30. Visualize Work** URL: https://entrowise.com/principles/visualize-work Make work, workflow, and bottlenecks visible to the entire team and system. Visibility is a prerequisite for understanding, managing, and improving flow. Hidden backlogs and invisible queues signal this principle is violated. **31. Limit Work in Progress (WIP)** URL: https://entrowise.com/principles/limit-wip Actively constrain the number of items in progress at any stage. WIP limits expose bottlenecks, reduce multitasking, and improve flow and quality. Everyone is busy but nothing gets finished signals this principle is violated. **32. Manage Flow** URL: https://entrowise.com/principles/manage-flow Focus management attention on the smooth, predictable movement of work through the system rather than on keeping people busy. Flow management prioritizes outcomes over activity. **33. Make Policies Explicit** URL: https://entrowise.com/principles/make-policies-explicit Surface and document the rules that govern how work is selected, prioritized, and handled. Explicit policies enable consistent decisions and make system behavior understandable. Inconsistent prioritization and ad-hoc decision-making signal this principle is violated. **34. Small Batches** URL: https://entrowise.com/principles/small-batches Process work in the smallest viable increments to reduce risk, improve flow, and accelerate feedback. Large batches hide problems, create queues, and delay learning. Quarterly releases and large feature bundles signal this principle is violated. --- ## About Entrowise Entrowise is a coaching and advisory practice specializing in problem-centric coaching for software delivery and technology leadership. Founded by Gourab Nanda. The practice helps technology and project leaders move beyond reactive firefighting to deliberate, principle-driven decision making using the PPA Method. Website: https://entrowise.com Email: gourab@entrowise.com Phone: (800) 909-3738 --- ## Site Map - Home: https://entrowise.com/ - PPA Method: https://entrowise.com/ppa-method - Principles Library: https://entrowise.com/principles - AI Coaching Agent: https://entrowise.com/AI-diagnostic-coaching-tool - Leadership Coaching Workshops: https://entrowise.com/leadership-coaching-workshops - Enterprise Consulting: https://entrowise.com/enterprise-consulting - About: https://entrowise.com/about - Contact: https://entrowise.com/contact