A team behind schedule receives a message about taking ownership. The principle may be relevant, but the team still needs to know what it can decide, which commitments remain fixed, and how to resolve a dependency held elsewhere. A useful message should make those questions easier to answer.
Leadership quotations compress an idea into something memorable. They can remind people of an agreed approach or open a discussion. Their limitations appear when the sentence is expected to settle choices that depend on context, authority, and resources.
Applying a principle therefore requires more than repeating it consistently. The organisation needs to explain what the principle means in a particular case, how it interacts with other responsibilities, and what evidence will show that it helped. Consider a company introducing a customer portal while maintaining its existing service. Several familiar sayings could guide the work, provided each is connected to a commitment people can carry out.
‘Empower the Team’ Needs a Defined Decision Boundary
The portal team needs room to make implementation choices without seeking approval for every detail. It also needs to understand which decisions affect obligations outside its remit. Selecting a layout differs from changing who can authorise a customer request.
The sponsor should identify what the team may decide, which requirements remain fixed, and where a new decision is required. Those boundaries should reflect consequences, rather than the status of the person asking. A small change can be consequential if it alters access or a customer promise.
Delegation also requires information and capability. The team needs the relevant requirements, access to users, and enough expertise to assess alternatives. Handing over an outcome while withholding those conditions can create responsibility without a workable route to fulfil it.
Atlassian’s DACI framework distinguishes the person driving a decision from its approver and contributors. It provides one way to discuss participation, but the named roles must match actual authority. A project lead cannot commit another team’s capacity merely because a chart describes them as accountable.
For the portal, a useful arrangement might allow the team to choose an approach within an agreed scope and budget, while changes to approval rights return to the service owner. The team should know what information that owner needs and how a delayed answer affects delivery.
Review how the delegation works in practice. Are routine choices made at the intended level? Do exceptions reach someone able to act? Does the sponsor override local decisions without explaining the change? Those examples provide a better test of empowerment than whether employees are described as autonomous.
‘Embrace Failure’ Needs an Account of Acceptable Exposure
A team testing an unfamiliar portal workflow may learn that users interpret a step differently from the designers. A prototype can reveal that misunderstanding before it affects real requests. The unsuccessful design is useful evidence because the test was bounded and the question was clear.
A live service making incorrect approvals creates different responsibilities. The organisation needs to prevent harm, detect errors, recover records, and communicate appropriately. Describing every unwelcome outcome as learning would obscure those consequences.
Before encouraging experimentation, establish what can be tested, with whom, under which controls, and who may approve the exposure. Identify the evidence needed and the point at which the trial should stop or change. The plan should include what happens to any data or commitments created during it.
A feature being reversible in software does not mean every effect can be undone. Customers may already have acted on an incorrect response, or staff may need to repair records. Recovery needs to account for the service as well as the interface.
Google SRE’s discussion of postmortems illustrates a method for examining incidents and contributing conditions without reducing the investigation to individual blame. Its operational context does not make every mistake equivalent, but it shows why learning needs evidence and follow-up.
The portal sponsor can support that approach by distinguishing an authorised trial from a missed responsibility and by committing capacity to corrective work. An invitation to learn is less credible if every finding is followed by an unexplained penalty or if agreed improvements remain unfunded.
‘Lead by Example’ Should Refer to Observable Decisions
A leader’s behaviour can help establish what a principle means. The useful example is more specific than visible enthusiasm or willingness to work late. It shows how the leader handles a choice others will also face.
For the portal, the sponsor might acknowledge that a promised date depends on unresolved access rules. They can obtain the decision, revise the commitment where necessary, and explain the consequence to commercial colleagues. That demonstrates how to report uncertainty and reconcile obligations.
The same applies to requesting new work. If a leader adds a capability, they should address its effect on scope, timing, and capacity. Quietly treating executive requests as exceptions while expecting the team to protect the plan gives conflicting instructions.
An example also needs its context. A senior leader may have authority or support unavailable to a team member. Encouraging staff to copy the action without those conditions can be misleading. Explain what transfers and what route others should use when they reach their boundary.
A leader can demonstrate correction too. They might revise an earlier assumption, acknowledge information they missed, or change a process that is not helping. This supports an expectation of evidence-based judgement rather than an image of constant certainty.
Staff should still be assessed against their responsibilities, rather than a requirement to imitate a leader’s personality or working style. The principle concerns reliable conduct in the work. It does not require everyone to speak, organise their day, or present confidence in the same way.
‘People First’ and ‘Customer First’ Need Explicit Trade-Offs
Broad priorities can conflict in a specific decision. The portal may promise customers quicker access while requiring substantial preparation from a support team already maintaining the current service. A statement that both people and customers matter does not allocate that work.
Leadership needs to compare options. The company could narrow the initial release, provide cover, change the date, or adjust another commitment. Each option has costs, and the people controlling those commitments need to decide which consequences are acceptable.
The transition plan should include routine obligations. Existing customers still need help, and the old process may need support until records and responsibilities have moved. Future efficiency does not provide the capacity required for migration today.
Measures should reflect the combined result. A faster portal journey is less useful if unresolved cases move to an overloaded support queue. A high volume of completed tasks does not establish that customers receive an accurate response. Check the end-to-end service as well as local activity.
Employees’ concerns can inform the decision without automatically settling it. A support lead may identify a missing exception path; a customer may need a capability outside the planned scope. The organisation should examine those accounts and explain the choice, including when a request is declined.
This makes the principle more credible. Staff can see what it required in a difficult case and how competing obligations were handled. They do not have to infer which slogan will be invoked after the outcome is known.
Test the Principle Through the Work It Changes
A useful principle should leave a practical trace. The portal team can identify which decisions it holds, what trials are authorised, how new requests affect the plan, and where customer and operational evidence are reviewed. The trace may be a short decision note or a changed commitment rather than a new formal process.
Make the interpretation available to people who were absent when it was agreed. A principle can acquire a different meaning as it passes through teams, particularly where one group uses it as a statement of ambition and another treats it as an approved commitment. A short explanation with realistic examples can reduce that ambiguity.
The portal team might retain an example of a decision it can make locally and one that needs the service owner’s approval. When a new case arrives, staff can compare the consequence rather than guess from the phrase alone. The examples should be maintained when authority or scope changes. Old guidance can otherwise preserve an arrangement that no longer applies, leaving employees uncertain whether to follow the current plan or the most familiar leadership message. Keeping the meaning current is part of maintaining the principle in practice.
Choose a few cases and ask whether the principle helped. Did delegated authority avoid unnecessary delay? Did a trial resolve a genuine uncertainty? Did a concern reach an owner? Was a scope change reflected in the customer promise and delivery plan?
An unfavourable outcome needs interpretation. The principle may have been applied poorly, the arrangement may lack a necessary condition, or the proposed approach may be unsuitable. Do not assume that the team failed to demonstrate the right attitude simply because the result disappointed.
Executive accountability belongs in that review alongside the team’s actions. Leaders control parts of the environment in which the principle is applied, including resources, priorities, and the response to uncertainty. Those decisions should remain visible.
Quotes can continue to serve as shorthand once the working meaning is understood. A reminder to take ownership can be helpful when people know the responsibility and have the means to act. The sentence becomes useful because it points back to an arrangement the organisation maintains, with enough evidence to revise that arrangement when it stops helping.
