Innovation Leadership: 6-Month Operating Plan. Innovation leadership rarely fails because leaders lack ideas. It fails because good intentions stay abstract: leaders say innovation matters, yet calendars, budgets, meeting agendas, and decision rights still reward business as usual. The most useful response is not another innovation slogan or a longer strategy deck. Choose one leadership principle, turn it into an operating routine, and visibly model it for six months.
The strategy–execution gap is persistent because strategy is often clear at the top but disconnected from the work people actually do. Research summarised by Atlassian found that while 80% of leaders said strategic priorities were clear, only 11% could show that at least three-quarters of portfolio work was explicitly linked to those priorities; 72% also identified competing priorities as a chronic source of team overload. Innovation leadership, therefore, is less about generating more initiatives and more about creating the conditions for the right work to receive attention, resources, and honest decisions.
Choose One Principle
Start deliberately narrow: choose one principle and make it operational for six months. Trying to implement four principles at once usually produces a well-written framework but little behavioural change. A single principle, applied consistently, clearly signals what leadership now values.
Choose from these four:
Protect Strategic Time: Dedicate specific calendar segments to safeguard essential work focused on innovation, skill development, and initiatives that could significantly shape the organisation’s future. Protected time will give teams uninterrupted opportunities to brainstorm, strategise, and develop new concepts without the distractions of daily operational demands.
Make Resource Criteria Visible: Clearly outline and share the criteria and evidence used to allocate resources, including personnel, financial investments, and focus areas within the organisation. Transparency: Make the strategic alignment of projects with organisational goals clear. By making organisational decision-making standards visible, you build stakeholder trust and enable informed discussions about resource allocation.
Kill Underperformers Visibly: Proactively terminate projects that fail to meet previously established performance criteria. This process should be conducted transparently, explaining to all relevant parties why these decisions were made. Provide insights into the evaluation process to ensure everyone understands the reasoning behind ending support for certain initiatives, and to encourage a culture of accountability.
Engage Deeply on 3–5 Defining Projects: Focus leadership efforts on a select few initiatives with the potential to impact the organisation substantially. By focusing on 3 to 5 projects, leaders can allocate attention, resources, and energy more effectively. This focused engagement will enable deeper exploration, stronger collaboration, and more innovative outcomes, ultimately guiding the organisation’s transformative change.
Each principle addresses a different failure mode. Protecting strategic time counters urgency bias. Visible resource criteria counter opaque politics. Killing underperformers counters sunk-cost thinking. Deep engagement on a few defining projects counters fragmentation. Together, they form a coherent innovation operating system. Start with the one that will create the most useful disruption in your context, then move to the next only after the first is established.
Protect Strategic Time
Protecting strategic time means treating future-oriented work as a real commitment, not a discretionary activity to sacrifice when operations get busy. It requires a named time block, a defined purpose, clear attendance expectations, and protection from routine operational escalation.
A practical version is to establish a weekly or fortnightly Strategic Innovation Block for the leadership team. For example, dedicate two hours every Tuesday morning, labelled “Strategic Innovation Block,” on all leaders’ calendars. The agenda might include:
- Reviewing prioritised customer problems,
- Assessing prioritised innovation experiments and their learning progress,
- Identifying capability gaps, and
- Agreeing on next steps for the highest-priority initiatives.
Use a meeting template with these sections and circulate a decision log after each session. Leaders should model this commitment by attending consistently and deflecting operational requests to other forums. Reinforce the purpose by sharing before-and-after stories of a project that advanced because of this protected time.
Success is not measured by how many ideas were discussed. It is whether the organisation protected capacity for work that would otherwise never receive attention. If strategic time is repeatedly cancelled, postponed, or consumed by operational issues, the principle has not yet been operationalised; discipline is established.
Make Resource Criteria Visible
Visible resource criteria turn innovation investment from a matter of influence into a matter of evidence. People should be able to see what a project must demonstrate to receive more funding, staffing, or executive sponsorship.
Create a simple one-page investment standard. Include criteria such as:
Strategic Fit: Clearly identify and articulate the specific strategic priority that the initiative aims to address. Provide context on how this aligns with the broader organisational goals and vision, ensuring that its relevance to the overall strategy is easily understood.
Customer or User Evidence: Summarise the supporting data or research findings that demonstrate user or customer demand for the proposed initiative. This may include survey results, user feedback, market analysis, or case studies that reflect the target audience’s needs and preferences and robustly substantiate the proposal’s rationale.
Feasibility: Assess and outline any technical challenges or resource-related risks that could impede the initiative’s successful implementation. Consider technological constraints, skill shortages, operational hurdles, or market conditions that could affect execution.
Expected Value: Provide a detailed estimation of the potential impact the initiative could have on the organisation. This may include financial projections, improvements in customer satisfaction, increases in market share, or gains in operational efficiency. Include qualitative and quantitative metrics to give a comprehensive view of anticipated benefits.
Resource Requirements: Outline the critical resources necessary for successful project execution. This includes a detailed breakdown of required funding, the specific skills or expertise needed from team members, and the estimated time commitment required from stakeholders throughout the project’s lifecycle.
Next Decision Gate: Clearly specify the criteria and evidence required to progress to the next decision-making phase of the initiative. This may include completing market validations, securing necessary resources, or running pilot tests. Clarifying this ensures all stakeholders understand what must be achieved to move forward.
For example, attach a template to all new proposals and require completion of each section. In review meetings, display these criteria on-screen and score each proposal together. Every
Publish the criteria before decisions are made, not after. Then use the same criteria in every funding conversation. When leaders apply the standard inconsistently, people learn that influence matters more than evidence. When they apply it consistently, the organisation has shared language. If weak work persists, stop it visibly once the criteria are embedded.
Kill Underperformers Visibly
Killing underperformers visibly is one of the hardest and most valuable innovation leadership behaviours. Projects often continue not because they are promising, but because someone has invested reputation, time, or political capital in them. A leader who refuses to stop weak work quietly signals that activity matters more than impact.
Operationalise killing criteria in ads. Operate the Makele stakeholders. For example: if a project misses two consecutive evidence gates, fails to attract user adoption after three months in market, cannot demonstrate a plausible path to value, or is deprioritised in strategy review, it triggers a formal stop-or-pivot review. Use a standardised template to document the lessons and redeployment plans for any released capacity. Hold these reviews as open forums—invite representatives from impacted teams and communicate outcomes in the next all-hands. Emphasise that the purpose is to free up resources for higher-impact work.
Visibility does not mean humiliation. It means transparency. Explain what was learned, what will be redeployed, and why stopping is a responsible use of organisational resources. An innovative organisation should include defined checkpoints where leaders decide whether to continue, pivot, or kill an initiative. With clear decisions, leaders can shift attention to the few projects that matter most. Then engage deeply where needed.
Engage Deeply on 3–5 Projects
Deep engagement means leaders don’t just approve innovation projects from a distance. They personally understand the 3–5 most important initiatives: the problem, assumptions, evidence, risks, resource needs, and decision points.
This concentration matters because attention is a resource. When leaders spread themselves across too many projects, every team receives shallow guidance and slow decisions. When leaders focus on a small portfolio, they can ask better questions, remove blockers faster, and make trade-offs with real context.
Select projects that meet three tests: they connect to a strategic priority, they could create meaningful value if successful, and they require leadership attention to succeed. Use a shortlist or dashboard to track these 3–5 defining projects and make progress and blockers visible to all leaders. Assign each project a senior sponsor with authority to allocate resources, a decision cadence (such as biweekly checkpoints), and a clear operational owner. The sponsor should attend key project reviews and regularly communicate progress and decisions to the broader organisation, not to micromanage, but to support informed decisions and quickly unblock issues. Once you set this focus, embed it in normal processes and routines.
Embed It in Processes
A principle becomes operational when it appears in the organisation’s inner workings: calendars, project templates, meeting agendas, decision rights, and performance conversations.
For example, if you choose visible resource criteria, embed them in the project intake form, quarterly investment review, business-case template, and leadership meeting agenda. Display these criteria on an internal site and train managers to use them. If you choose to protect strategic time, place it in the executive calendar, protect it in scheduling policy, and make attendance a leadership commitment rather than an optional invitation. Periodically audit calendar use and publish attendance rates to reinforce accountability.
The test is simple: could a new leader join the organisation and understand how work gets done? If the principle exists only in a presentation, it is aspiration. If it appears in recurring processes, it is an operating principle. From there, build a rhythm that keeps the principle active over time and puts it on the regular review schedule.
Build Organisational Rhythms
InnovOrganizationalythm. Without a recurring cadence, decisions drift, priorities blur, and teams return to urgent operational work. A six-month operating plan should establish a predictable rhythm of review, decision, and course correction.
A useful rhythm is:
- Weekly: Protect strategic time and review the defining projects.
- Fortnightly: Check evidence, blockers, and resource needs.
- Monthly: Review the portfolio against the published criteria.
- Quarterly: Decide whether to fund, pivot, stop, or scale.
- At six months: Assess whether the principle changed behaviour and outcomes.
This cadence should be lightweight. The purpose is not to create more reporting; it is to create decision points. Strategy execution improves when organisations turn objective strategy into resources and tracked action rather than leaving strategy as a high-level intention. The result should be clearer choices, faster trade-offs, more time directed to the work that matters most, and a visible shift in how innovation gets decided and delivered. With the rhythm in place, measure whether it is changing behaviour and outcomes.
Measure the Right Things
Measurement should fundamentally address two critical questions: First, has the adopted principle effectively bridged the gap between strategy and execution? Second, has it successfully liberated time and resources to focus on groundbreaking work? The tangible benefits become evident when an organisation aligns its goals and actions more precisely, creates space for transformative projects, clarifies decision-making, and minimises distractions that compromise attention.
After six months of implementing these principles, the most apparent outcomes include a noticeable shift in how leaders allocate time, distribute resources, and decide which initiatives to discontinue. At this stage, the key question is whether these principles have been seamlessly integrated into daily practices and behaviours across the organisation.
Avoid the pitfall of measuring only activities. For instance, simply counting workshops conducted, ideas submitted, or meetings held can create a superficial illusion of innovation without real strategic progress. Instead, organisations should track a carefully selected set of outcome and behaviour metrics that offer deeper insights. Each metric should be clearly defined, including how data will be gathered—such as through project dashboards, calendar audits, and feedback surveys—and who in the organisation will report it. These metrics should then be reviewed in leadership meetings, with summaries shared with teams to maintain transparency and accountability.
Key metrics to monitor include:
Percentage of Active Work Linked to Strategic Priorities: Assess how much ongoing work aligns directly with the organisation’s core strategic objectives.
Utilisation of Protected Strategic Time: Measure the time spent on protected strategic initiatives versus intended use to assess time-management efficiency.
Speed of Resource Allocation in Response to Priority Changes: Track how swiftly resources are mobilised or reallocated when strategic priorities shift, highlighting the organisation’s agility.
Number of Projects Stopped, Pivoted, or Scaled: Count how many projects have been halted, redirected, or expanded based on predetermined criteria, indicating responsiveness to strategic needs.
Leader Participation in Defining Projects: Monitor leader engagement in the 3–5 key projects that define the organisation’s strategic direction to ensure top-level involvement.
Team Confidence in Transparency and Fairness of Innovation Decisions: Assess how confident team members feel regarding the legitimacy and openness of innovation decisions within the organisation.
At the six-month mark, conduct a thorough assessment of whether the implemented principles have led to tangible changes in behaviour and outcomes. Based on this evaluation, leaders should decide whether to maintain, adjust, or replace the current approach. The measures outlined should collectively show the ultimate benefits: improved alignment among team members, faster decision-making, and greater capacity to take on projects that will shape the organisation’s future trajectory.
Atlassian research highlights several diagnostic questions that can serve as valuable tools for organisations. These include questions about how much active work aligns with strategic objectives, how quickly resources can be reallocated amid changing priorities, and whether leaders can spot operational drift without a new reporting exercise. These diagnostic questions better indicate operational alignment than simply listing completed tasks. Using these questions can help organisations assess the effectiveness of their operational plans and guide them into the next six-month strategy execution cycle.
A Six-Month Story Arc
Month 1: Diagnose and Commit
Choose one principle. Name the problem it addresses. Identify the current evidence: where time is being lost, where resources are unclear, where weak projects persist, or where leadership attention is scattered. Publish a short commitment statement and define what you will operationalise by month six.
Checkpoint: One principle selected, baseline measures recorded, first process change scheduled.
Month 2: Design the Mechanism
Turn the principle into a concrete mechanism. This may be a protected calendar block, a published investment standard, a stop-review process, or a defining-project portfolio. Keep it simple enough that people can use it without training.
Checkpoint: Document the mechanism, assign an owner, and schedule first use.
Month 3: Run It in Public
Use the mechanism consistently and visibly. Leaders should attend, apply the criteria, make decisions, and explain their reasoning. Expect resistance, workarounds, and requests for exceptions. Don’t abandon the principle at the first sign of discomfort; treat those moments as evidence that the old operating system still dominates.
Checkpoint: First real decisions made using the mechanism; exceptions and friction points logged.
Month 4: Correct the Course
Review what is working. If operations are consuming strategic time, tighten the agenda or change the meeting format. If resource criteria are too vague, clarify the evidence required. If people avoid kill decisions, make the review smaller, faster, and more factual.
Checkpoint: One course correction implemented; measures compared with baseline.
Month 5: Scale the Behaviour
Extend the principle beyond the leadership team. Teach managers how to use the same criteria, protect the same time, or apply the same decision discipline. The aim isn’t uniform bureaucracy, but shared practice.
Checkpoint: At least one team or business unit is using the mechanism independently.
Month 6: Review and Institutionalise
Assess the results honestly. Did the organisation work? Did it reallocate time toward breakthrough work? Did leaders make faster, clearer decisions? Did weak projects stop earlier? Then decide whether to deepen the same principle, add a second principle, or adjust the mechanism.
Checkpoint: A written six-month review, a decision on the next principle, and a revised operating plan.
Course Corrections
Course correction is not failure; it is the mechanism that makes the principle durable. If people treat strategic time as optional, reduce attendance and make the output a decision, not a discussion. If resource criteria feel bureaucratic, reduce them to five questions and apply them consistently. If killing projects feels politically dangerous, begin with a small, low-stakes project and demonstrate that stopping work can be respectful, evidence-based, and productive.
The important discipline is to change the mechanism, not the principle. For example, if “visible resource criteria” isn’t changing behaviour, don’t quietly abandon transparency. Instead, ask whether the criteria are too complex, whether leaders are bypassing them, or whether the decision forum lacks authority. Then repair the process.
Publish Your Operating Plan
The call to action is direct: select one principle and publish your six-month operating plan. The plan doesn’t need to be long. One page is enough if it contains the principle, the problem, the mechanism, the cadence, the owner, the measures, and the month-by-month checkpoints.
For example: “For the next six months, we will make resource criteria visible. We will assess every innovation investment request against five published criteria. We will review the portfolio monthly and make fund, pivot, stop, or scale decisions quarterly. Success means more work linked to strategic priorities, faster resource reallocation, and at least two evidence-based stop-or-pivot decisions.”
That kind of statement changes innovation leadership from a value statement into an operating commitment. It tells people what leaders will do, how they will do it, and how they will be held accountable. The execution gap translates strategic intent into clear objectives, aligned measures, ownership, and recurring decision rhythms.
Choose the principle that will create the most useful discomfort. Make it visible. Protect it in the calendar. Test it in real decisions. Then, after six months, ask not whether you talked about innovation leadership, but whether your organisation is different because of it.
This Post is 20/20. Tomorrow’s post will be the first in the series titled: Leading with Clarity: 30 Practical Lessons for Managers and Lifelong Learners.
