A senior program manager at a large organization is responsible for three initiatives launching in the same quarter. An AI transformation automating claims review. An ERP rollout replacing a decade of spreadsheets. A custom application for a new product line. Three kickoff decks, three timelines, three teams moving fast.
Not one of the three kickoffs included a single conversation about which principles actually mattered for that specific initiative. Flow got a mention. Quality got a mention. Nobody stopped to investigate what this particular kind of work would actually put at risk.
That is the more common failure, and it is quieter than getting the principles wrong. Most leaders never ask the first question at all.
The First Discipline: Investigate Before You Execute
A principle driven leader does not walk into a kickoff assuming they already know which principles apply. They investigate. What kind of initiative is this, really. What has historically gone wrong in initiatives like it. Which of the five dimensions of delivery, flow, learning and adaptation, governance and accountability, system integrity, human-AI collaboration, is most exposed here, before a single sprint starts.
This is the actual starting point for most leaders, not a refinement for people who already have it figured out. Entrowise has spent real time researching principles across all five of those dimensions specifically because most leaders have never had a structured way to ask the question. The principles library exists as a place to start that investigation, not finish it.
Most of what the library holds is close to universal. Flow principles, learning and adaptation principles, governance principles, they apply to almost any delivery scenario, whether the team is shipping software, rolling out a system, or automating a process. A leader does not need to reinvent this every time. What changes, and what the investigation is actually for, is which of those universal principles carries the most weight for this specific initiative.
AI Transformation. Most of the usual principles still apply, but the investigation surfaces a question most teams have not asked: once the AI has been right a few times, does the organization quietly stop checking it? That question points straight at Agent Trust Must Be Continuously Earned Not Historically Assumed and Traceability Must Be Designed In Not Added After, two principles from the Human-AI Collaboration dimension that carry far more weight here than they would on a typical software project.
ERP Implementation. The investigation surfaces a different question: are departmental policies actually written down, or does everyone just know how things work until the system forces a decision nobody agreed on? That points to Make Policies Explicit and Accountability Must Match Control, Governance and Accountability principles that matter everywhere but become load bearing the moment a rigid system starts enforcing decisions people never formally made.
Custom Application Development. The investigation surfaces a question about whether the team actually knows if what they are building still solves the right problem, or whether they stopped checking a few sprints ago. That points to Frequent Feedback Loops and Empiricism, Learning and Adaptation principles that matter in any delivery context but become the difference between a product that adapts and one that quietly drifts when nobody outside the team is dictating the requirements.
The Second Discipline: No Principle Survives Contact With Reality at 100 Percent
Investigation only gets you the right principles. It does not get you full adherence to them, because real constraints exist and they are not going away because a principle says they should.
Take Accountability Must Match Control. The investigation for an ERP rollout correctly names it as load bearing. But now put that principle inside an organization with a genuine Structural constraint, team boundaries and ownership gaps that have existed for years and cannot be redrawn before this project ships.
A leader without diagnostic training treats this as a binary. Either the principle is honored or it is abandoned. A principle driven leader asks a sharper question: given this specific structural constraint, to what degree is this principle currently being compromised, and what is that compromise actually producing?
In this case, the honest answer is often that the people closest to the decisions carry maybe sixty percent of the real authority their accountability requires. The consequence is not abstract. It shows up later as an Unintended System Condition, most often Accountability Fragmentation, where the people held responsible for an outcome were never given the control to prevent it.
Naming that compromise honestly, in the room, before it becomes a postmortem finding, is the entire value of the second discipline.
What Principled Implementation Actually Is
It is not applying more principles, and it is not applying them with perfect weighting from day one. It is two disciplines, done in order. Investigate what applies to this specific work before assuming you already know. Then diagnose, honestly, how far your real constraints will let you go, and name the consequence of the gap before someone else discovers it for you.
Questions Worth Asking Before the Next Kickoff
What kind of initiative is this, and which dimension of delivery is most exposed by its nature?
Has anyone actually investigated which principles apply here, or has the team defaulted to the usual list?
For the principles that matter most, which real constraint, structural, incentive, governance, capability, dependency, or political, limits how fully they can be honored?
Given that limit, what is the honest percentage of adherence, and what Unintended System Condition does the remaining gap produce if nobody names it?
Most leaders do not fail their principles. They never investigate which ones were theirs to fail in the first place, and when reality inevitably falls short of the principle anyway, nobody says by how much or what it costs.
Principled Implementation starts with a question, not a checklist: which principles are actually mine to watch here, and how honestly can I say I am watching them.