Can a commitment to values replace written rules, or does flexibility become a recipe for inconsistency and public distrust? Imagine two organizations: one runs on spoken norms, personal honor, and informal rituals; the other publishes a short code, measures outcomes, and meets regularly to review how the rules are working. Which one do you trust more when things go wrong?
At first glance this is a small question about process. Under the surface lies a deeper tension about how skilled professionals govern themselves: do values suffice, or must we formalize conduct to preserve trust at scale? This piece argues that the debate is not binary. The real insight is procedural: the most durable systems combine a light, living code with continuous inspection and adaptation. That insight comes from an unlikely synthesis of two worlds: agile practice in technology and the rising demand for formal ethics rules in high trust institutions. Read on for a practical framework that turns values into enforceable learning loops, plus concrete actions you can apply to teams, boards, or courts.
The paradox of values and rules: why both feel right and both feel wrong
Many professionals prefer norms over rules. Norms are portable. They let experts exercise judgment. They are adaptive to unique contexts and they preserve professional dignity. But norms also create variability. When the public or stakeholders encounter inconsistent behavior, they lose confidence. The problem grows with size and complexity.
Contrast that with rules. Rules promise clarity and accountability. They make expectations explicit and enable measurable compliance. The downside is that rigid rules can ossify practice, encourage box checking, and punish necessary judgment. Rules without context become blunt instruments.
This is the paradox: values make practice humane and adaptable. Rules make practice predictable and auditable. Too much reliance on one side produces a pathology: either arbitrary behavior with eroding trust, or brittle practice that cannot adapt to new problems.
A useful analogy comes from craft and manufacturing. In small craft shops, master artisans pass down tacit knowledge and norms. In industrial settings, managers developed standardized work to guarantee consistent quality across thousands of parts. Standardization did not kill craftsmanship. Instead it turned variability into a controlled variable, allowing improvement and innovation to be measured and scaled. The same dynamic plays out in professional bodies that face scrutiny: without a portable, testable standard, norms fray when under pressure.
What agile practice reveals about governing professionals
Agile thinking was born as a reaction to heavyweight, rule heavy ways of building complex systems. It emphasized individuals and interactions, working outcomes, and responsiveness to change. The movement distilled a few guiding values and a set of lightweight practices to increase learning speed.
But the story does not end with values alone. The most successful agile teams adopt simple artifacts and routines to create reliable outcomes: short feedback cycles, explicit roles, clear definitions of done, and public commitments. Those elements are not heavyhanded rule making. They are minimal standards that make the values operative and measurable.
Two further points about agile practice matter for governance beyond software:
Values need operational scaffolding to scale: A manifesto of principles is a compass. To steer a ship you also need a rudder and a map. Agile provides both through recurring ceremonies and visible work in progress. Those practices make it possible to detect when the team drifts from its values.
Standardization is the engine of improvement: Standard work in manufacturing created a baseline from which to experiment. In agile teams, a standard definition of quality or completion enables meaningful retrospection. Without a shared yardstick, teams cannot learn what worked and what failed.
These lessons explain why many organizations that openly champion flexibility nonetheless adopt light rules. The rules serve learning and accountability, not control for its own sake.
The governance design that blends values and enforceability
If we accept that both values and rules have essential roles, the next question is practical: how do you design governance that preserves discretion while creating consistent outcomes? I propose a three part governance model you can apply to teams, professional bodies, or courts. Name the model the Principles Practices Feedback loop.
Principles: Start with a short set of high level commitments that capture the spirit of the institution. These are value statements, easy to remember and hard to misinterpret. They are the north star.
Practices: Translate each principle into a small set of observable behaviors and simple artifacts. Practices are the minimum standard for putting a principle into action. They must be lightweight enough to adopt quickly and concrete enough to be inspected.
Feedback: Create regular, external facing feedback loops that evaluate both compliance and the principle that motivated the practice. Feedback includes metrics, periodic reviews, and a mechanism for corrective action that is transparent and proportional.
This loop is designed to be iterative. Practices evolve from the feedback cycle so they remain fit for context. The model aims to avoid two ruinous outcomes: neglecting practice and relying only on rhetoric, or imposing rigid rules that destroy discretionary judgment.
Concrete translation: how a code might look in practice
Imagine designing a short ethics code using this model. The code itself contains a few crisp principles. Each principle has one or two corresponding practices. Each practice has a named metric and a cadence for review.
Example principle: Avoid conflicts that could undermine public confidence.
Practice: Publish annual recusal criteria and a public ledger of recusal decisions. Require notification within a short window when potential conflicts arise.
Feedback: Quarterly audit of recusal compliance, plus an annual public summary that aggregates recusal reasons and responses without revealing confidential details.
Example principle: Maintain impartiality in public communications.
Practice: Define allowable external comments and require pre clearance for political donations or campaign related activities. Use a short checklist to capture potential perception risks.
Feedback: Rapid complaint triage with a transparent process and a yearly disclosure of actions taken.
Two design constraints matter here: minimalism and iterativeness. The code should be as short as possible while being actionable. The review process should seek to iterate every cycle. This aligns with agile wisdom: small, testable rules plus fast feedback beat large, static codes that no one reads.
Practical mental models and tools to operationalize the loop
Below are three mental models and a practical toolset that help translate the governance loop into everyday practice.
Mental model 1: Standardize to enable judgment
Standardization is not the enemy of judgment. Instead, it creates a baseline from which deviation is visible and therefore defensible. If you document what counts as acceptable practice, then when someone exercises discretion outside that range they can explain why the deviation was the right response. Standards create permission to innovate responsibly.
Mental model 2: Make ethics inspectable, not only admirable
Values are noble when expressed; they gain force when they are observable. Convert important norms into a small number of observable practices. Treat those practices like tests. You cannot pass a test you never administer.
Mental model 3: Use short cycles for learning and public trust
Long review cycles hide problems until they become crises. Short cycles reveal issues early when corrections are easier and reputational damage is limited. Public institutions especially benefit from cadence. Frequent transparency builds trust cumulatively.
Practical tools
A light code document: One page with 4 to 6 principles and an appendix that links each principle to 1 or 2 practices. Keep the language concrete.
A visible ledger: A simple public record of certain actions that matter to stakeholders. For courts this could be recusal entries. For teams this could be exceptions to deployment practices.
A retrospective rhythm: A scheduled forum to look back at the last period, focusing on what rules were followed, why exceptions occurred, and what to change. Make summaries public when appropriate.
Metrics that matter: Choose 3 to 5 metrics that reflect both compliance and the spirit of the principle. Avoid vanity metrics. For example, measure time to resolve complaints, percentage of recusal notifications completed on time, and user reported trust levels.
What this approach makes possible, and what it still cannot fix
When you design governance like a learning system you get several gains. First, you reduce the space for ad hoc behavior that erodes trust. Second, you create a defensible record that explains discretionary choices. Third, you enable improvement because you can measure what you change.
But do not expect governance mechanics to solve all problems. People are human and incentives matter. A code is only as effective as the people who enforce it and the incentives embedded in the institution. Transparency without enforcement can be performative. Metrics without context can be gamed. That is why the feedback loop must include independent review or audit when stakes are high. Autonomy cannot be total; accountability must be credible.
A final caution: avoid the temptation to over engineer. The most useful codes are short and alive. They are not legal novels. They are living practice guides that evolve through small experiments and public learning.
Key Takeaways
Translate values into minimal, observable practices: A principle without a practice is a slogan. Create one measurable practice for each core value.
Use short feedback cycles: Inspect practice frequently and adapt. Publish summaries so stakeholders can see progress and failures.
Standardize to increase discretionary judgment: Make baseline expectations visible so exceptions require explanation, not cover.
Keep the code short and living: Start with a one page code linked to a small set of metrics and a review cadence. Iterate based on data and public feedback.
Ensure credible review: Pair public transparency with an independent mechanism that can enforce or recommend corrective action when needed.
Conclusion: rules as tools, not enemies of trust
The instinct to trust professionals and rely on norms is noble. The public demand for clear rules is legitimate. Neither instinct is wrong. What matters is design. A short living code, coupled with visible practices and tight feedback, preserves the dignity of discretion while making behavior predictable and reviewable. Think of rules not as shackles but as scaffolding: they support the skilled work of professionals and create the surfaces on which real learning can happen.
Values without inspection are wishes. Rules without iteration are chains. The sweet spot is a light code that invites continuous learning.
If we want institutions that are both wise and trustworthy we must stop treating values and rules as enemies. Instead we should treat them as partners in a disciplined process of learning and accountability. That is the practical promise of applying agile thinking to the hardest problems of professional governance.
