Execution
Core
A complete methodology for building momentum through daily execution — drawn from behavioral science, media operations, and real-world creative infrastructure.
Stacking Wins
Method
Small, completed actions compounded over time produce identity change, not just results. This framework is the operational foundation of every system in this ecosystem.
What It Is
The Stacking Wins Method™ is a structured daily execution protocol built on one principle: completed actions accumulate into identity. Not big swings. Not launch days. Not viral moments. Wins are the smallest unit of completed work that moves a project, system, or outcome measurably forward.
A "win" is not a result you receive. It is an action you complete. The distinction matters because you cannot control outcomes — you can only control execution. This framework redirects focus from results to completions, which are fully within your control.
Wins are categorized, tracked, and reviewed. Over time, they build a verifiable record of execution — which changes how you see yourself, and how others engage with your work.
The Foundation
"You don't rise to the level of your goals. You fall to the level of your systems. Stacking wins is the system that makes discipline automatic."
"Every completed win is proof. Enough proof, collected daily, becomes identity. Identity becomes behavior. Behavior becomes results."
The 5-Layer Win Stack
Each day is structured around five categories of wins. Not every layer fires every day — but intentional execution means hitting at least three.
What the Research Says
This framework is grounded in three behavioral science principles. First: self-efficacy theory (Albert Bandura) — belief in one's ability to execute is built through accumulated evidence of past performance, not through affirmations. Every logged win adds to that evidence base.
Second: identity-based habit formation — behavioral research consistently shows that sustainable behavior change happens when actions are tied to identity ("I am someone who executes daily") rather than outcomes ("I want to make more money"). The Win Stack builds the identity layer first.
Third: completion bias — the brain releases dopamine upon task completion, not task initiation. Small, completable wins create a neurochemical feedback loop that makes continued execution feel rewarding rather than effortful. The system works with your neurology, not against it.
The Operational Logic
Most execution frameworks fail because they demand large, sustained outputs before delivering any feedback. The Stacking Wins Method™ inverts that sequence. It delivers feedback — a logged, verified completion — immediately and repeatedly.
The categorization of wins (Foundation, Build, Revenue, Relationship, Clarity) solves another common failure: effort without coverage. It's easy to spend a full day creating content and miss the revenue action entirely. The five-layer structure prevents blind spots.
The cumulative record function is what separates this from a simple to-do list. When you can see 60 days of logged wins, you have operational proof of your own capability. That proof is the most powerful motivator in the system.
Creators, Media, and Business
| Context | Foundation Win | Revenue Win | Build Win |
|---|---|---|---|
| YouTube Channel | Upload scheduled video on time | Add CTA to description + pin comment with link | Complete one thumbnail A/B test |
| Consulting Agency | Respond to all active client comms | Send one follow-up to open proposal | Document one repeatable SOP |
| Personal Brand | Post daily content piece | Include product link in one post | Draft one framework or article section |
| Digital Products | Check analytics / keyword triggers | Send one email to product list | Add one new email to sequence |
| Media Operation | Publish one piece of scheduled content | Invoice or follow up on pending deal | Build out one content format or template |
How It Lives in the New Agenda / Planner
- Five labeled fields at the top of each daily page — one per win category. The operator enters their single intended win per category before the day starts.
- Completion checkboxes — each field has a box to mark complete at day's end, not at the start. The act of checking creates the neurochemical signal.
- Win Count tracker at the bottom of each daily page — a running total across the week. Operationalizes the "stacking" metaphor visually.
- Weekly Win Review — a dedicated page spread at the end of each week prompts a category-by-category review: which wins consistently got skipped? That pattern is the bottleneck.
- 90-Day Win Stack log — a full grid page at the back of the planner. One row per day, five columns. Makes the cumulative record visible and tactile.
How It Drives Money and Results
The Revenue Win category is the direct economic engine of this framework. Most operators underearn not because their offer is weak, but because revenue-generating actions get deprioritized in favor of creation and building. The Win Stack mandates a revenue action every day — even a small one.
At the consulting level (RGM), the Stacking Wins Method™ is installed as the client's daily operating protocol during onboarding. Clients who can't identify their five wins on Day 1 of engagement have already revealed their primary bottleneck: lack of operational structure, not lack of ideas or effort.
Over a 90-day engagement, the log becomes a business audit. You can see exactly where execution is consistent, where it breaks down, and which category of win is being chronically skipped. That data drives the next recommendation.
Self-Evaluation
Why People Break the System
Applied in Practice
A content creator with a 12K TikTok following, a pending digital product, and two social media management clients has been operating reactively — posting when inspired, pitching when desperate, building when the mood is right. Revenue is inconsistent. She knows what she needs to do but can't get traction.
She installs the Win Stack. Day 1, she maps her five wins: Foundation — post one piece of content; Build — write one page of her digital product; Revenue — send the invoice she's been delaying for 11 days; Relationship — reply to three DMs with real responses, not just likes; Clarity — decide and document her posting schedule for the next two weeks.
By Day 14, she has a log. By Day 30, she can see that Relationship and Revenue are consistently the last things she does — and some days, she skips them entirely. That visibility changes her day structure. Revenue moves to morning, before any content work.
By Day 60, the log is proof. Not that she's successful — but that she executes. When she raises her rate, the log is part of the internal evidence she uses to hold the conversation without discounting.
Momentum
Index
Momentum is not a feeling. It's a measurable operational state — a compounding ratio of consistent action to time. This framework gives you a number, and a system for interpreting it.
What It Is
The Momentum Index™ is a self-scored diagnostic and operational tool that measures your current execution velocity across four domains: Output, Consistency, Coverage, and Compounding. The Index generates a score between 0–100 that reflects not how you feel about your work, but how your work actually looks over a defined time window.
The Index is not a motivation tool. It's a diagnostic. A high Index score does not mean you're thriving emotionally — it means your operation is moving. A low score identifies where execution has stalled, not why you should feel bad about it.
The Momentum Index™ is reviewed weekly, used to calibrate effort allocation, and referenced whenever a major decision needs to be made about capacity, opportunity, or strategic direction.
The Foundation
"You cannot feel your way into momentum. You have to execute your way in. The Index tells you whether you're moving or standing still — regardless of how it feels."
"Momentum compounds. The difference between someone who scores 40 and someone who scores 75 isn't talent. It's the number of days in a row they kept the machine running."
The Four-Domain Scoring Model
Each domain is scored 0–25. Total score = 0–100. Scored weekly, tracked monthly.
Total score interpretation:
| Score Range | State | Operational Meaning | Recommended Action |
|---|---|---|---|
| 0 – 25 | Stalled | Execution has broken down. Likely a structural or environmental cause, not a motivation problem. | Reduce scope. Return to one Foundation Win per day only. Rebuild from the bottom. |
| 26 – 50 | Moving | Execution is inconsistent or siloed. Work is happening but not compounding. | Identify which domain is lowest. Target that domain specifically for the next 7 days. |
| 51 – 74 | Building | Solid operational momentum. Blind spots exist but the machine is running. | Shore up the weakest domain. Begin planning capacity expansion or next offer tier. |
| 75 – 89 | Operating | High-functioning execution. Results are compounding. This is the target state. | Protect what's working. Take on one new initiative only. Watch for over-extension. |
| 90 – 100 | Compound | Peak operational state. Every domain is firing. This is rare and typically short-duration. | Document the conditions that produced this score. Build systems to replicate them. |
What the Research Says
The Momentum Index™ applies two distinct bodies of research. The first is behavioral momentum theory — originally developed in clinical psychology — which holds that the probability of completing a difficult behavior is significantly increased when preceded by a sequence of easier, successfully completed behaviors. The Index measures whether that sequence is intact.
The second is compounding systems theory as applied to productivity research — the finding that the rate of return on consistent behavior is nonlinear. Small improvements in execution frequency produce disproportionately large gains in output over 60–90 day windows. The Compounding domain in the Index is specifically designed to detect whether this nonlinear effect is activating.
The scoring structure (four domains, equal weighting) is informed by balanced scorecard methodology — the principle that single-metric performance measurement consistently produces blind spots. An operator who tracks only output volume will optimize output at the expense of coverage or consistency, undermining the compounding effect entirely.
The Operational Logic
Most operators have an intuitive sense of whether they're "on" or "off" — but intuition is unreliable, especially during high-stress or high-distraction periods. The Index replaces intuition with data. You know your score. The score is not open to interpretation.
The four-domain structure prevents the most common form of self-deception in performance systems: collapsing all effort into one category and calling it momentum. An operator who creates content seven days a week but sends zero revenue actions will feel like they're moving — their Index will tell them they're not building.
Weekly scoring creates a lag indicator — you're measuring the last seven days, not the last hour. This prevents score gaming through one intense session and accurately reflects operational velocity over a meaningful time window.
Creators, Media, and Business
The Index functions differently at different business stages. Here's how it applies across common operator contexts:
| Business Stage | Target Index Score | Primary Focus Domain | Red Flag Signal |
|---|---|---|---|
| Pre-Launch / Build | 45–60 | Consistency + Build | High output, zero revenue actions |
| Active Launch | 65–80 | Coverage + Revenue | Score drops mid-launch — execution has broken down |
| Client Delivery | 55–70 | Consistency + Compounding | Low Compounding — deliverables aren't building on each other |
| Scale Phase | 70–85 | Compounding + Coverage | Score plateaus — adding volume without depth |
| Maintenance / Steady State | 60–75 | Consistency | Consistency drops below 5 consecutive days |
How It Lives in the New Agenda / Planner
- Weekly Review Page — a dedicated spread at the end of every 7-day block. Four scored domains displayed as labeled fields with 0–25 ranges. Total score calculated at bottom.
- Domain bar display — each domain has a simple fill-in bar (5 segments of 5 points each). Visual representation of the week's performance by category — instantly shows which domain is weakest.
- Monthly Index tracker — a four-week grid showing Index scores by domain. Allows the operator to see trajectory: is the score climbing, holding, or declining over time?
- State label prompt — after scoring, the operator circles one state word (Stalled / Moving / Building / Operating / Compound) and writes one sentence: what produced this score this week?
- Index-to-Action bridge — a small decision tree printed below the tracker: "If Consistency is lowest → move one revenue action to 9am tomorrow." Simple, non-interpretive. Removes the need to strategize from a low-state position.
How It Drives Money and Results
In a consulting engagement, the Momentum Index™ functions as the client's weekly health metric. During RGM onboarding, the first Index score is the baseline — not a judgment, but a starting point. The engagement is structured around moving the score into the 65–80 range by Week 6.
The Index is also used to time strategic decisions. If a client's Index is below 50, they are not a candidate for adding new offers, platforms, or team members — regardless of how excited they are. Low-momentum operators who scale add complexity before stability, which collapses both.
At the product level, the Momentum Index™ can function as a premium feature in a digital product or group program: participants submit weekly scores, and the operator (you) provides group coaching responses based on the pattern of scores across the cohort. High scalability, low time investment.
Self-Evaluation
Why People Break the System
Applied in Practice
A media consulting agency owner closes three clients in Q1 — her biggest quarter to date. Entering Q2, she expects momentum to carry forward. Instead, she feels scattered. Client delivery is eating all her time. No new content is going out. No outreach happening. She's busy, but something feels off.
She runs her first Momentum Index. Output: 18/25 (lots happening). Consistency: 20/25 (showing up daily). Coverage: 10/25 (all effort in client delivery — no Build, no Revenue actions). Compounding: 8/25 (client work is isolated, not building toward anything new). Total: 56/100 — Building state, barely.
The score tells her something her feelings couldn't: she's not stalled, but she's running on two of five cylinders. The lowest domains are Coverage and Compounding. The fix is not to work harder — it's to reintroduce one Revenue Win and one Build Win per day, even if small.
Four weeks later, her score is 74. She hasn't worked more hours. She's allocated better. By Week 8, she has one new proposal out, one new piece of content infrastructure built, and a clarity win that removes a recurring bottleneck in client onboarding. The Index didn't tell her what to do — it told her where the gaps were so she could make that call herself.