How to Know Which Path Is Right for You

"I'll get promoted by next year."
"I'll land the job by end of year."

One of the biggest source of stress I see in my clients is that they set a goal on something they can't control, and then they put a timeline on it.

You might get promoted someday. But promoted by next year? That part isn't yours to decide.

You can do everything right. You can be exactly the person who deserves it. And a budget freeze, a reorg, or one person's opinion can still take it off the table.

You already know the advice here. Focus on what you can control. That part is easy to say. The hard part is that it doesn't tell you what to actually do.

Because there are so many paths in front of you. Get the certification. Deliver the big project. Build your network. Each one sounds reasonable. So which is the right one?

Most people turn it into a probability game. If I get this credential, my odds go up. If I nail this project, I'll stand out. That's not wrong. But it keeps your whole sense of whether you chose well tied to an outcome you still don't control.

So I ask something different.

What if you do all of it, and you still don't get what you wanted? How would you feel?

The answer isn't the same for every path. And that difference is the whole thing.

For some paths, the honest answer is that it was wasted. I didn't want another certification. I wanted the job. I gave up my evenings, my weekends, time with my family, my own health, and it bought me nothing.

For other paths, the answer is different. Even without the outcome, I'd have grown. I'd be a sharper professional and a bigger person. I'd have elevated my own ground, so the options I can't even see yet would open up. And it was fun. I did my best. I have no regret.

That second kind of path is the right one for you.

Not the one with the best odds. The one you'd still be glad you walked, even if it never pays off the way you hoped.

I found my own version of this question a long time ago.

As a kid, I thought hard about what I wanted to be, and I narrowed it down to two. One was archaeologist. Digging up evidence of ancient civilizations felt thrilling. The other was physicist. Understanding how the whole universe works sounded incredible. I went back and forth for a long time.

Then one day I asked myself a strange question. If I never became the archaeologist or the physicist, if I just cleaned their research buildings, would I still be happy?

My gut answered before I could think it through.

For archaeology, cleaning the building felt like nothing. But for physics, sweeping the floors of that building still felt like being part of it. Still contributing, in some small way, to how humans come to understand the universe. That still meant something to me.

So I chose physics.

I spent about twenty years there. Undergrad, graduate school, a postdoc. And then I left.

I still don't have any regret. I had fun. I learned more than I can measure. I met my husband there, and made friends I still have. Physics is how I found my way into data science, which became my career. And it's why I get to sit here now and tell you this story, and hopefully help you find your own answer.

None of that was the outcome I set out for. And all of it was worth it.

That's the test. Not "which path gives me the best shot at the thing I want?" It's "which path would I still choose if the thing I want never comes?"

The paths that only pay off when you win leave you fragile. The one that pays off either way is where your real ground is.

If you never got the outcome you're chasing, which path would you still be glad you walked?

The McKinsey 7-S Framework: A Simple Guide to Aligning Your Organization

Most strategies don't fail because they're wrong. They fail because the rest of the organization isn't built to support them.

You can have a brilliant plan, but if your structure, systems, and people aren't aligned with it, the plan stays on paper. This is the problem the McKinsey 7-S Framework was designed to solve.

Developed in the late 1970s by Tom Peters and Robert Waterman at McKinsey & Company, the 7-S Framework identifies seven internal elements that need to work together for an organization to succeed. It has outlasted decades of management trends because it answers a question that never goes out of style: why isn't this working the way we thought it would?

It's also a powerful way to share your vision and influence leadership. Whether you're making the case for change in your current role or walking into a job interview, the 7-S Framework gives you a structured way to demonstrate strategic thinking — to show how you see the whole organization, not just your piece of it.

What the 7-S Framework Is

The model maps seven interconnected elements of an organization. Change one, and the others feel it. The seven elements are grouped into two categories:

Hard elements (easier to identify, easier for leadership to influence directly):

• Strategy — your plan for competing and winning
• Structure — how the organization is arranged (reporting lines, departments, hierarchy)
• Systems — the daily processes and tools that get work done

Soft elements (harder to pin down, shaped by culture):

• Shared Values — the core beliefs at the center of the organization
• Style — how leadership shows up and operates
• Staff — the people and their general capabilities
• Skills — the specific competencies the organization has

Shared Values sit at the center of the model. Every other element depends on them. When values are clear and lived, the rest of the system has something to organize around. When they're not, the other six elements drift.

Breaking Down the Seven Elements

1. Strategy

Your strategy is how you plan to build and maintain a competitive advantage. It answers:

• What are we trying to achieve?
• How will we respond to competition and shifts in the market?
• How does our strategy adapt to changing customer needs?

Strategy only works when the rest of the organization is built to execute it.

2. Structure

Structure is the architecture of your organization: who reports to whom, how teams are divided, where decisions are made.

• Is decision-making centralized or decentralized?
• How do departments coordinate?
• Where are the formal and informal lines of communication?

A structure that worked at 10 people often breaks at 50. A structure that supports innovation can be the wrong fit for scale.

3. Systems

Systems are the processes and tools that keep daily work moving — financial systems, HR processes, communication platforms, project management workflows, decision protocols.

• What systems do we rely on most?
• How are they monitored?
• Where are the bottlenecks?

Outdated systems quietly drain energy from every other part of the organization.

4. Shared Values

Shared Values are the core beliefs and standards that guide behavior. Not the values posted on the website — the ones actually lived day to day.

• What do we genuinely stand for?
• What does our culture reward and tolerate?
• How strong and consistent are these values across the organization?

When shared values are vague or contradicted by behavior, every other element gets harder to align.

5. Style

Style refers to leadership and management approach. It includes how leaders communicate, make decisions, and handle conflict.

• Is leadership collaborative or directive?
• Do teams actually function as teams, or are they groups in name only?
• How effective is leadership at modeling what's expected?

Style shapes culture more than any mission statement.

6. Staff

Staff is about the people in the organization — who's there, what roles exist, and where the gaps are.

• What roles and specializations do we have?
• What positions are missing?
• How are we developing the people we have?

Staff decisions shape what the organization is capable of becoming.

7. Skills

Skills are the specific capabilities the organization is known for — what it actually does well.

• What are our strongest competencies?
• Where are the skill gaps?
• How do we monitor and grow skills over time?

Skills and Staff sound similar but answer different questions. Staff is who you have. Skills is what they can do.

When to Use the 7-S Framework

The framework is useful any time you need to understand how the pieces of an organization fit — or why they don't. Common applications:

• Improving performance in a team or company that feels stuck
• Implementing a new strategy
• Navigating a merger, acquisition, or major restructure
• Onboarding new leadership
• Diagnosing why change efforts keep stalling
• Aligning a fast-growing team that's outgrown its original setup
• Making the case for change to senior leadership in a structured, credible way
• Preparing for a leadership interview, where you want to demonstrate strategic thinking about the organization you're hoping to join

It works at the organization level, but also at the level of a department, team, or project.

How to Apply It

Here's a practical sequence:

Step 1: Start with Shared Values. Are they clear? Are they consistent with your current strategy, structure, and systems? If not, name the gap.

Step 2: Examine the hard elements. Look at Strategy, Structure, and Systems together. Do they reinforce each other, or are they pulling in different directions? A growth strategy paired with a structure built for stability is a common mismatch.

Step 3: Examine the soft elements. Style, Staff, and Skills. Do they support what the hard elements are trying to do? A strategy that requires bold decision-making won't work under a leadership style that punishes risk.

Step 4: Identify the misalignments. Where are the contradictions? Where is one element undermining another?

Step 5: Adjust and reassess. Change one element, and the others shift. This is iterative, not linear. Expect to circle back.

A simple way to track alignment: list the seven elements in a grid and check whether each pair supports the other. Mismatches are where the work is.

A Quick Example

Imagine a small company of five people. The founder's values shape everything. Strategy is clear. Structure is informal but functional. Systems are off-the-shelf and adequate. Everything aligns because it's small.

Now imagine that company at 30 people, selling into new markets. The original strategy has evolved, but the structure hasn't. New hires don't fully understand the founding values. Systems built for five people are buckling. The skills that made the early team successful aren't the skills needed now.

Nothing is broken on its own. But the pieces no longer align. A 7-S analysis surfaces this — not as a list of problems, but as a pattern. From there, the leader can make targeted changes: clarify values for new hires, evolve the structure, upgrade systems, build the missing skills.

That's the value of the framework. It turns a vague sense that something is off into a specific, addressable picture.

A Few Honest Limitations

The 7-S Framework is a diagnostic tool, not a prescription. It tells you where things are out of alignment. It doesn't tell you what to do about it. Two organizations with the same misalignments may need very different solutions depending on context, history, and people.

It's also a snapshot. Organizations are dynamic, and alignment is never permanent. The framework is most useful when revisited periodically — especially during growth, change, or strategic shifts.

Final Thought

The 7-S Framework endures because it reflects something true about organizations: success isn't about getting one thing right. It's about getting many things to work together.

When strategy, structure, systems, values, style, staff, and skills reinforce each other, performance follows. When they contradict each other, no amount of effort in one area will fix what's misaligned across the others.

This is also why the 7-S Framework is such a useful tool when you're trying to influence others. Walking into a leadership meeting — or an interview — with a 7-S lens shows you understand how organizations actually work. You're not just pitching an idea. You're showing how the pieces fit.

If something in your organization feels stuck, the 7-S Framework is a good place to start asking why.