If you’re asking how the GPS+I framework handles week 3 — the solutions week — you’ve already done something most people working through transformational programs quietly skip past: you’ve stopped assuming that finding the answer is the same as actually being ready to use it, and you’ve started wondering what makes a solution land differently when you’ve earned your way to it.

Most of us, when we hear “week of solutions,” think of a delivery. Someone hands you the answer, you write it down, and now you have it. That’s not what week 3 is. And if it were, you’d already be free — because you’ve collected more solutions in the last decade than most people will see in a lifetime. The 50+ books on your shelf are full of them. The folder of unfinished courses is full of them. It’s not that you’ve been missing answers. It’s that the answers have been arriving without the conditions they need to actually take root.

Week 3 is about creating those conditions. Let’s walk through what that actually looks like.

What week 3 sits between

The GPS+I framework moves through four weeks: Goals, Problems, Solutions, and Integration. Each week earns the next. Week 1 names where you’re going with enough honesty that your nervous system can feel it. Week 2 names what’s actually in the way — not the surface complaint, but the underlying pattern that keeps re-installing the same outcome. By the time you arrive at week 3, you’ve done something rare: you’ve defined the problem at the level it actually lives at, not the level it usually gets described at.

That’s important, because solutions are only as useful as the problem they’re matched to. A pricing solution for what’s actually a visibility wound will keep failing. A visibility solution for what’s actually a receiving wound will keep failing. The reason most “solutions” feel like they don’t work isn’t that they’re bad — it’s that they were never built for the real problem in the first place.

Week 3 begins from the assumption that the problem has been named properly. If it hasn’t, you loop back. There’s no shame in that. The framework is designed to be cyclical, not linear.

What week 3 actually does

Three things happen in the solutions week, and they happen in this order on purpose.

First, you generate options — without committing to any of them yet. This sounds small but it changes everything. Most of us, when we identify a problem, immediately reach for the first solution that feels familiar. That reflex is the pattern. Week 3 deliberately slows it down. You list out three to five possible ways the problem could be addressed — including ones that feel uncomfortable, unfamiliar, or “not how I do things.” The point isn’t to pick yet. The point is to widen the field so the choice you eventually make isn’t a reflex.

Second, you check each option against your actual constraints — body, life, and capacity. A solution that looks elegant on paper but requires a nervous system you don’t currently have is not a solution for this week. It’s a solution for a future you. This is where people most often misuse standard advice. They pick the most aggressive option because it sounds the most decisive, and then they spend three months trying to drag a dysregulated system into a strategy it can’t hold. Week 3 explicitly asks: which of these options can the version of me who exists right now actually sustain?

Third, you choose one — and only one — and you define what doing it looks like in concrete behaviour. Not as a goal. As a practice. “I will raise my prices” is not a week 3 outcome. “Starting Monday, every new enquiry hears the new number, and I will notice what happens in my body when I say it” — that’s a week 3 outcome. The solution becomes a series of small, observable actions, not a wish.

Why this is so different from “just pick a strategy”

The deeper move in week 3 is that solutions get treated as experiments, not verdicts. You’re not deciding what’s true forever. You’re choosing one honest test, running it for a defined period, and gathering real data about how your system responds.

This matters more than it sounds. A lot of the over-functioning, perfectionism, and threshold self-sabotage that show up in people with adverse childhood experiences come from a deep, often-unconscious belief that every choice is final and every misstep is catastrophic. Week 3 is structurally designed to push against that. A solution isn’t a marriage. It’s a hypothesis. If it works, you keep it. If it doesn’t, you’ve learned something specific, and you re-enter the loop with better information.

This is also where the 6-Layer Model often gets layered in. A behavioural solution that ignores the somatic layer will fail. A narrative solution that ignores the relational layer will fail. The solutions week asks you to be honest about which layers your chosen option is actually addressing — and which ones it’s quietly skipping. That alone closes the gap between knowing and doing more than any new technique ever could.

What “success” in week 3 actually looks like

It’s not that you’ve solved the problem. It’s that you’ve chosen one honest experiment, you’ve matched it to the right layer, and you’ve built a small, repeatable practice that lets you learn from contact with reality. That’s it.

If you finish the week with a sustainable practice and a clear sense of what you’re noticing, you’ve done it well — even if the outer result hasn’t shifted yet. The shift is being built underneath.

From there, week 4 — integration — takes whatever you learned and weaves it back into how you actually live, so the work doesn’t stay in a notebook. And then the cycle starts again, at a new altitude, with a new goal that the previous loop made possible.

If something in this is landing, and you’d like to walk through a full GPS+I cycle with people who are doing the same work — naming real goals, real problems, and choosing solutions their bodies can actually hold — you’re welcome to come and try the Skool community for free. There’s no pressure to arrive ready. That’s exactly the point.