Strategic Thinking Program

Think past your job description

A self-paced online program for individual contributors who already notice things: recurring complaints, mismatched processes, decisions that don't quite make sense. This program gives that noticing a structure, a proposal format, and a path to the people who can act on it.

Self-paced modules   Cohort discussion calls   One real proposal by the end

Individual contributor reviewing a cross-department pattern diagram at a desk, dramatic side lighting
Pattern Spotting One-Page Proposals
Why individual contributors get stuck

Good observations die in team chat

Most individual contributors spot a problem long before it reaches a manager's desk. They see it in support tickets, in the way two departments hand off work, in a report nobody reads twice. The observation is usually right. What's missing is the format that makes it land.

This program is not about becoming a manager. It is about learning to move an idea from "that's annoying" to "here is a decision worth making," and knowing which of those ideas are worth the effort to push.

Close-up of hands mapping a cross-department process on a glass whiteboard wall
What the program covers

Five working skills, not five lectures

Each module is built around a single practical skill you can apply the same week, not a theory you file away.

Spotting Patterns Across Departments

How to notice when a problem in your team is actually a symptom of something happening two or three departments over, and how to confirm it before you say anything out loud.

Framing Observations as Opportunities

The difference between "this process is broken" and "this is costing us time we could recover." Same observation, different reception in the room.

The One-Page Proposal

A format for putting an idea in front of someone with decision authority: the problem, the cost of ignoring it, the option, and what you're asking them to do.

How Decisions Actually Get Made

The org chart tells you who has a title. It rarely tells you who signs off, who gets consulted informally, and whose disagreement quietly kills a proposal.

Choosing Which Battles to Fight

Not every valid observation is worth raising this quarter. A method for weighing effort, timing, and political cost before you spend your credibility.

How the program is structured

Four stages, one proposal to show for it

The modules build in order. By the end you're not holding a certificate, you're holding a document you could actually send.

01

Watch & Notice

Structured observation exercises across a live process in your own workplace. You're not brainstorming, you're documenting what's actually happening.

02

Reframe & Document

Turn a list of complaints into a short, evidence-based description of a business opportunity, written in language a director will read past the first line.

03

Propose & Pitch

Build your one-page proposal using the program template, then rehearse how you'd walk someone through it in five minutes or less.

04

Navigate & Sustain

Map the informal decision path in your organization and decide, deliberately, whether this is the moment to raise it or the moment to wait.

Where this shows up at work

Different roles, the same missing skill

Strategic thinking is not reserved for people with "strategy" in their title. It shows up wherever someone is close enough to a process to see what's actually wrong with it.

Data analyst noticing a recurring pattern on a laptop screen in a dim office

Data & Reporting Analysts

Sees the same anomaly appear in three monthly reports before anyone connects them to a shared root cause.

Two colleagues from different departments comparing notes over a shared document

Operations Coordinators

Notices a vendor handoff that wastes two days every cycle, but has never had a format to raise it above team level.

Small group workshop session discussing strategy around a table with notes

Customer Support Specialists

Hears the same complaint worded five different ways and recognizes it as a product decision, not a training issue.

Executives in discussion during a decision-making meeting in a bright conference room

Engineers & Technical Leads

Understands why a recurring bug keeps returning and can trace it to a process gap, not just a code fix.

Hands mapping a cross-department process diagram on a glass wall

Finance & Planning Analysts

Sees a budget mismatch repeat across regional teams and needs a way to frame it before the next planning cycle.

Common questions

Before you book a call

No. The program is built specifically for individual contributors, people without a team reporting to them. The skills taught (pattern spotting, proposal writing, reading decision flow) don't require a title, only proximity to a real process.

Modules are self-paced. Most participants spend a few hours per week on the exercises and readings, plus one scheduled discussion call. The pace is set by you, not by a fixed weekly deadline.

The program teaches a way of thinking and a proposal format. What happens after you submit a proposal depends on your organization, your manager, and factors outside this program's control. We describe a process, not an outcome.

One full module is dedicated to reading how decisions actually get made in your specific workplace, including the informal channels. Part of the work is deciding whether now is the right moment, or whether it isn't yet.

No. The frameworks apply across office-based roles in most industries: technology, operations, finance, customer service, healthcare administration, and similar fields. Examples in the materials are drawn from a range of workplace settings.

That's outside the program's reach. What the program provides is preparation: a clear document, a rehearsed pitch, and a realistic read on timing. The internal response is up to your organization's own process.

Ready to put a name on what you've been noticing?

A discovery call is a short conversation to see whether the program fits where you are right now, no obligation attached.

We use cookies to run this site and, with your permission, to understand how it's used. See our Cookie Policy.

Essential

Required for basic site function. Always active.

Analytics

Helps us understand how pages are used.

Functional

Remembers choices such as form entries.

Advertising

Used to measure the relevance of outreach.