Decision · Control · Influence

A simple model to navigate responsibility

Many EAs carry outcomes without owning the authority behind them. The result is not "too much work" — it's constant interpretation: What is mine? What is delegated? What requires approval?

The DCI framework gives you a practical way to categorise situations and respond with the right level of ownership — without over-owning responsibility.

Get the framework See examples

Built for real stakeholder environments (VP level, multi-site operations): clarity before action, reduction over complexity.

The core idea

Not every request is a "yes/no" task question. Most are actually a responsibility question. DCI helps you choose the right response pattern by separating three forms of work.

Decision Mode

You decide and act independently because you have context and authority. Outcome ownership is clear.

Own it
Act fast
No back-and-forth

Control Mode

You steer a process and create clarity, but the final decision sits elsewhere. You manage the path, not the outcome.

Steer it
Escalate early
Document

Influence Mode

You cannot decide, but you can shape direction through framing, options, and stakeholder alignment.

Advise
Frame options
Protect boundaries

How to classify a situation in 30 seconds

Use these questions to avoid "silent liability" — where responsibility shifts to you without being explicit.

Decision check

  • Do I have enough context to decide without guessing?
  • Do I have explicit authority to decide?
  • If this goes wrong, is it clearly owned by me?

If all three are "yes" → Decision Mode.

Control vs. Influence check

  • Am I expected to steer a process (timelines, follow-ups, coordination)?
  • Or am I expected to shape direction (options, framing, alignment)?
  • Where does the final approval / decision formally sit?

Steering path → Control Mode. Shaping direction → Influence Mode.

Rule of thumb

If you feel pressure to "just handle it" but you cannot clearly name authority and ownership, you are not in Decision Mode. You are either steering (Control) or shaping (Influence).

Response language by mode

DCI is not just a model — it's a communication shift. Below are subtle, senior-safe sentence patterns you can reuse.

Decision Mode

When you can own the outcome.

  • "Understood — I'll proceed with X and confirm once done."
  • "I'll take ownership and move this forward."
  • "I'll decide based on the current context and keep you posted."

Control Mode

When you steer, but don't own the final decision.

  • "Current status: X. Next step: Y. Decision needed from Z."
  • "I can coordinate the process — who owns the final approval?"
  • "I'll track this and escalate if we miss the deadline."

Influence Mode

When you shape direction through framing and options.

  • "Two options: A (fast) vs B (safer). Recommendation: A."
  • "If the priority is speed, I suggest X. Risk: Y."
  • "I can draft the framing for stakeholders if helpful."

Boundary language (subtle, non-defensive)

Use when responsibility is trying to shift to you without authority.

  • "Happy to coordinate — to stay aligned, who owns the final decision?"
  • "Based on the current information, the decision sits with X. I can prepare options."
  • "I can proceed once we confirm the decision criteria."

Examples from real EA situations

The same task can sit in different modes depending on authority and context. Here are common patterns.

Situation Mode What you own How you respond
"Please schedule this meeting." Decision Time slots, logistics, invite sent "Understood — I'll schedule and confirm."
"We need an update from three stakeholders." Control Follow-ups, timeline, escalation path "Status is X. I'll follow up today and escalate if needed."
"Should we involve Legal now?" Influence Framing, options, recommendation "Option A: involve now (safer) vs B: later (faster). I recommend A."
"Can you own this deliverable?" (unclear scope) Control / Influence Clarify ownership before accepting outcome "Happy to coordinate — who owns final approval and success criteria?"
"Just decide what's best." (no authority) Influence Decision support, not the decision "I can propose the best option and risks — final call sits with you."

Why this matters

Most overload comes from mode confusion: deciding without authority, controlling without escalation rules, influencing without clear framing. DCI reduces that cognitive load by making ownership explicit.

FAQ

Short answers, practical focus.

Is this productivity advice?

No. The primary outcome is role clarity — which often improves speed as a side effect.

What if my executive expects me to "just know"?

That's exactly where Control/Influence language protects you: you mirror context, clarify decision ownership, and propose options without sounding insecure.

Can I use this in any industry?

Yes. DCI is role-logic, not company-specific process guidance.

How long does it take to apply?

You can start immediately. The work is not "learning"; it's applying the mode lens to daily situations.

Ready to apply this beyond theory?

The full EA Operating System includes workbooks and templates designed for immediate use: decision prompts, escalation clarity, boundary language, stakeholder mapping.

<