Leadership systems · Bozeman, Montana

The problem isn't usually the problem.

What keeps coming back lives a level deeper, in how decisions get made and reinforced.

That is where I work. It is also where AI adoption holds or stalls, because adoption runs on leadership before it runs on technology.

Everything here comes down to a better relationship between people and their work.

Consulting · The leadership system

The spring at the summit shapes everything downstream.

When a problem keeps coming back, someone in the building usually already knows why. The work is finding where that knowledge stops before it reaches a decision, and repairing that.

At the summit of every organization is a spring: the leadership system. It is where direction forms and decisions originate. The quality of that source, how clearly authority is defined, how truth travels, how behavior is reinforced, determines the quality of everything that flows downstream.

This is not strategy design. It is leadership system design.

You may recognize this pattern.

The organization is capable. The people are committed. And yet:

  • Decisions that should take two days take three weeks.
  • The same problems surface in every leadership meeting, repackaged, not resolved.
  • The CEO is in every critical call.
  • Commitments are made and missed, absorbed without consequence.
  • Information arrives that should change the next decision, and the next decision does not change.

This is usually a system problem, not a talent problem. And systems can be changed when the right layer is examined.

Surface fixes do not hold.

When performance stalls, organizations reach for frameworks, workshops, or cultural resets. Many are useful. But without adjusting decision standards and reinforcement, they do not hold.

Stalled decisions, recurring political behavior, poor escalation, and unreliable forecasts are rarely talent problems. More often, people have learned what to raise and what to keep quiet from what actually gets rewarded.

Behavior follows what is reinforced, not what is announced.

You can see it everywhere but in your own house.

Capable leaders read other organizations with ease. The companies of friends, the board you sit on, the competitor across town, you can usually name what is wrong in an afternoon. The one system you cannot see clearly is your own, because you are standing inside it, and the fluency that makes you good at the work makes the blind spot more convincing. This is not a gap in ability. It is what proximity does to judgment.

An outside read is the instrument for that. Not advice, and not a second opinion confirming what you already suspect, but a disciplined look at the system you are too close to see, from someone with no stake in the current arrangement.

How I work.

I work with leadership teams to examine how decisions are actually made, how accountability is reinforced, and what assumptions are shaping behavior beneath the surface. We count what it is costing in your own numbers, and we test small changes before anything is rolled out.

Decision quality drives risk exposure. Risk exposure drives execution reliability. Execution reliability drives financial performance.

The lever that holds is rarely morale. It is what leaders pay attention to, measure, and reward.

When the work calls for AI, it runs through the same spine. That engagement model is the AI Operating Partner.

AI Operating Partner
More on this

Execution problems are patterned. They appear in decision breakdowns long before they show up in financial results.

The work moves through two phases. Phase 1 finds where the problem lives and what it costs. Phase 2 tests the change and installs it.

Before engagement · no fee

The first conversation

Before any engagement, a first conversation. No fee. No commitment. It is meant to help with something real, and to find out whether a real system-level problem is present. If more work looks useful, a second conversation is with you directly: what each of us wants, what each of us will and will not do, and plain notice that the work will look at the leadership team itself, you included.

If the conversation surfaces something worth examining, we define the scope of Phase 1. If it does not, you leave with a clear framework to pressure-test your next move, and no follow-up pitch.

Either outcome is a success. The point is clarity.

Phase 1 · Diagnosis

Phase 1, Discovery

We start with the problem that is costing you and trace it back through the people closest to it: who knew first, what they did with it, and where it stopped. That includes the managers in the middle, and people who raised it before, some of whom may have left.

This phase examines:

  • Where decision quality degrades under pressure
  • Where authority is ambiguous or duplicated
  • Where escalation hesitates or fails entirely
  • Where accountability requires constant intervention
  • Where truth moves too slowly to prevent failure
  • What assumptions are shaping behavior beneath the stated values

We count what the problem has already cost, with your finance lead holding the pen and only the numbers they would defend to a board. Not a forecast.

Objective: to find where the truth about the problem stops before it reaches a decision, and whether that is really what is costing you.

If the real limit turns out to be something else, such as too few people or a missing skill, I say so, and the work changes or stops there.

Outcome: a short written map of where the problem lives, my best explanation with the strongest alternative beside it, and what it has cost so far. Before you see it, a second practitioner reviews it and argues the other side.

Then we work through it with your leadership team in three sessions, starting small. The team corrects the map and makes it its own. The last session ends with a plain choice: make the change, keep things as they are knowing the cost, or turn toward what is really in the way. Each answer is a good outcome.

Phase 2 · Install & reinforce

Phase 2, System Reset

With the diagnosis in hand, we change the system. Not one grand intervention, but a small number of deliberate moves, each designed to reveal as much as it improves.

This is where most change efforts go wrong. A leadership system is not a machine with a broken part. It is a set of reinforcing relationships, and no one can fully predict how it will respond to change, including me. So each move is small, behaviorally specific, and instrumented. The system's response is not noise. It is the next piece of the diagnosis.

The moves may include:

  • Clarifying decision rights and authority
  • Resetting escalation norms: what requires a decision versus what requires information
  • Embedding accountability into operating cadence as a structural feature, not a follow-up ritual
  • Aligning incentives and reinforcement signals with stated performance standards
  • Adjusting the leader behaviors that are reinforcing the current pattern

Each move is written down before it starts: the change, who owns it, one thing you will do differently as CEO to back it, and what would tell us to expand it or stop it. Check-ins read each move as holding, fragile, regressing, or stalled, and no move is judged before it has had time to work.

The engagement closes when you have made the change your own in front of your team and the team can work the next problem this way without me. I come back at ninety days and at nine months to read the numbers with your finance lead.

Outcome: change measured in your own numbers, against the cost counted at the start. The nine month reading is the one that counts.

How commitment works.

Phase 1 is the only commitment made at engagement start. At the close of Phase 1, you have the map, what the problem has cost, and a clear choice about what comes next. Phase 2 is defined together at that point, not before. Stopping there is a good outcome.

No bundled total at signing. No pre-committed scope without a diagnosis. No obligation to continue if the work is not the right fit.

What this is not.

  • A framework implementation
  • A culture survey rollout
  • An open-ended advisory relationship

This work strengthens the leadership system where decision rights, human dynamics, and reinforcement intersect, the layer where strategy either translates into throughput or quietly stalls.

Adjusting tactics improves performance incrementally. Strengthening the leadership system shifts the ceiling.

If execution feels heavier than the strategy requires, the next step is clarity.

AI Operating Partner · An engagement model

Where the hours are.

Keep the judgment work. Fight for every hour the busywork takes.

The work that burns people out is usually work a system should carry. When a system carries it, speed, quality, and consistency go up, and the hours come back to the people who were carrying them: for better results, or for a better life outside the work.

Sort each task: busywork or judgment.

    Busywork
    • Quoting and estimating
    • Receivables follow up
    • Status updates
    • Document chasing
    • Scheduling

    18 hours back

    Judgment
    • A pricing call

    stays with a person

    More on this

    We find that work with one lens, busywork or judgment. We rank it by the hours it returns and build the highest leverage workflows first. The system takes the busywork. Your people keep the judgment calls. The hours that come back are counted.

    An engagement model inside the organizational work, not a separate practice. The discipline is the same one that runs through everything here: diagnose the system before changing it.

    This is one of two expressions of the same practice. The other is the consulting itself, and every engagement here runs on its spine.

    The diagnosis is the work.

    An AI project can only be judged against what the business said success looks like before anything was built. That is where this engagement begins.

    The first deliverable is a ranked map of where your operation is actually losing time, judgment, and margin, and which of those losses are structural rather than technical. That distinction determines everything downstream. Some friction resolves through a targeted build. Some friction is a decision-rights problem wearing a technology costume, and no tool will touch it.

    The map names the opportunity and what it is worth. What you do with it is your decision, and leaving with it is a legitimate outcome.

    What the work leaves behind.

    The models themselves are becoming a commodity. What does not commoditize is the accumulated judgment of your own business: your pricing logic, your customer history, the corrections your best people make without thinking about it. Captured, that becomes an asset that compounds. Uncaptured, it walks out the door every time someone retires.

    The work decides which AI to switch on and which to leave off, names who owns each approval, and puts that capture into how the company already operates, on the platform you have. An internal champion is trained to run it, and every correction they make feeds back, so the system gets more like your business and less like a generic tool. Month over month, the evidence is visible: corrections captured, edit rates falling, cycle times shrinking.

    The ongoing work is governance and judgment. What the system is permitted to decide, where a human stays in the loop, how it is audited, and what happens when the model providers ship a feature that replaces something you switched on. When that happens, you migrate onto it and redeploy the effort to the next thing. That is the job.

    You own all of it.

    Every prompt, every correction log, every evaluation, every dataset lives inside your systems and belongs to you. If we part ways, it stays with you, in full.

    This is the thing most companies should be asking about and almost none do. Institutional knowledge routed through a vendor's platform is knowledge you are renting. Ownership is also what makes the system auditable, and that matters more every quarter. Security and control are the leading reasons companies your size hold back, and the concern is a reasonable one.

    Where the leverage usually is.

    The best candidates are boring, judgment-heavy, and specific to you. Quoting and estimating, where the pricing instinct lives in one person's head. Receivables follow-up, where tone and relationship history decide whether the call lands. The work that is drowning someone competent, and that no off-the-shelf product understands because it depends on facts about your business alone.

    The work that is generic is not worth a system of its own. The model providers will ship it for free before long, and the right call is to switch theirs on and govern it.

    When the system in question is the one AI is about to inherit.

    The same discipline applies when a company is deciding what to automate. Most AI initiatives in companies this size do not fail on the technology. They fail because the tool inherits a system nobody examined, and then executes it faster.

    The AI Operating Partner engagement is that diagnosis, applied to the operation itself.

    Whatever gets switched on keeps one line: the system takes the busywork, your people keep the judgment calls, and the hours that come back are counted.

    Who this is for.

    Founder-led, privately held, and PE-backed companies between $20M and $200M in revenue, with a leadership team that is serious about the question and unconvinced by the noise around it.

    If the enthusiasm in the room is running ahead of the diagnosis, that gap is worth examining before anything gets built.

    Coaching · Individual leaders

    Leadership concentrates pressure.

    In the middle of all of it, one person can stall. Coaching gives that person a new vantage point: a place to think, and a way to see what is holding them in place.

    As responsibility increases, decision quality becomes more consequential. There are fewer places to think without consequence. Coaching provides that space.

    How I work as a coach.

    Coaching centers on decision clarity.

    Most leaders who feel stuck already know the choice they keep not making. The work is finding out what makes it feel impossible.

    We start with where you want to go. Then we walk back through the decisions you are making now until you reach the one that no longer makes sense to you. Sometimes a belief you have never tested is in the way. Sometimes it is time, or a skill, and I say so plainly.

    Each session ends with one small choice you make before the next, to find out whether that belief holds.

    How a leader interprets a situation determines how they respond. Repeated responses form habits. Habits shape how others experience the leader's authority.

    This is structured inquiry, not advisory. I do not tell leaders what to decide. I help them examine how they decide, and, when the work calls for it, who they are when they decide it.

    More on this

    Positioning

    Coaching is offered selectively, as a complement to consulting engagements, or for leaders navigating a specific inflection point. The work is demanding. It is reserved for clients whose situations warrant it.

    Most decision patterns are not really about the decision. They hold in place because of how a leader has come to understand themselves, what they believe they must be, protect, or prove. When a pattern keeps returning despite a leader knowing better, that is usually the level it lives at. The work goes there only when you choose to, because a leader is more than the sum of their decisions, and durable change rarely comes from the surface. It stays with the choices in front of you now, not your history.

    What an engagement looks like.

    Coaching runs in defined arcs, not open-ended relationships. A typical engagement is six months. It starts with where you want to go, in your own words, and one line on what you will be choosing differently. Between sessions the work continues, because the patterns under examination only show themselves under live pressure. The arc ends when you can do this work on your own, and three months later we read that line again together.

    Patterns this work addresses.

    • Hesitation in moments that call for decisive action.
    • Overextension, a leader running faster than the system can absorb.
    • Defensiveness when feedback or disconfirming information arrives.
    • Avoidance of the conversation, decision, or conflict the role actually requires.

    Relationship to consulting.

    Consulting strengthens organizational decision architecture and reinforcement systems. Coaching strengthens the leader's internal decision discipline.

    They are distinct, though the same principles run through both. An organization can have a well-designed decision architecture and still have leaders whose internal patterns undermine it. Coaching addresses that layer.

    Coaching is its own engagement, entered by the leader's own choice, not a phase of consulting and not something added to it. When a consulting engagement surfaces a pattern a leader wants to examine in themselves, that is an invitation, never an assumption. When a company pays for coaching, what is said in it stays with the leader.

    The practice

    One practice, two expressions

    I consult on the leadership system. I know AI systems from the inside because I have built them myself. I was an engineer before I was a consultant, and the order matters.

    Why both? Two frustrations most owners know: the problem your team keeps re-solving, and AI work that still feels too risky to start. They are usually the same problem, in how decisions get made and what gets rewarded. I work on both sides of it.

    The AI takes the busywork. Your people keep the judgment calls. The hours that come back are counted.

    The AI side opens with a short diagnostic that stands on its own and can end there.

    Same diagnosis, two sets of tools.

    The founder

    Zane Sigafoos

    Bio

    The leadership challenges I work on do not live in theory. They show up in execution pressure, in decisions that slow, in accountability that blurs, in leadership teams that work harder than the organization's actual complexity requires.

    For more than 13 years, I worked inside industrial, manufacturing, and operations environments where execution was the unit of work and leadership systems determined whether it held. I saw firsthand how small distortions in decision quality compound into operational drag. Over time, I became less interested in surface fixes and more interested in the systems producing the patterns.

    Summit Spring Partners was built from that experience. My work begins with how decisions get made and what gets rewarded, not with tools or typologies. I start with what the people closest to a problem already know, and where that knowledge stops before it reaches a decision.

    That same discipline informs my coaching work. With one leader, the question is the choice they keep not making and what holds it in place. With a leadership team, it is where the truth stops on its way to a decision. The principles are the same. The unit of work is different.

    I live and work in Montana. Summit Spring reflects a simple principle: if the source is strong, the system downstream is stable.

    Zane Sigafoos

    Background and training

    Education.

    M.A., Executive Coaching and Organizational Consulting, Townsend Institute. B.S., Mechanical Engineering, Colorado School of Mines.

    Experience.

    13+ years in leadership and operational roles across industries.

    Certifications.

    Working Genius. Crucial Conversations.

    The conversation

    Who this work is for.

    Leaders responsible for performance at scale. Founder-led, privately held, and PE-backed companies between $20M and $200M in revenue, where execution reliability fluctuates, accountability requires constant intervention, or cross-functional friction has a real cost.

    If performance feels harder than it should, the tension is worth examining.

    If you believe something beneath the surface deserves attention, a focused conversation is enough to determine whether this work is relevant.

    Start a Conversation