How I Think | Vanessa Smith

How I Think

How I work through a problem.

This is roughly the path I take a hard, unclear problem through, from the first vague symptom to a decision I can defend and a team that can run with it. It is the same approach whether the stakes are a local website or a much bigger call.

From a vague problem to a decision

01

Figure out the real question

I try not to jump on the presenting symptom. First I get clear on what is actually being asked and what a good answer would even look like.

02

Decide what matters

Not everything deserves equal weight. I separate the decision that moves the outcome from the noise around it and spend my time there.

03

Find the actual cause

Marketing is often where the problem shows up, but it is rarely where it starts. I trace the symptom back to the cause, because fixing the cause lasts and fixing the symptom does not.

04

Get the evidence straight

I prefer evidence over assumptions, so I gather it and weigh it before acting, and I say plainly when something is a judgment call rather than a fact.

05

Build the plan and the system

I design the plan and the system that runs it, so the answer holds up week after week instead of living and dying with one meeting.

06

Get people aligned

I get the people who have to live with the decision to agree on it before we commit. Alignment is part of the work, not an afterthought.

07

Make the call

When the evidence is clear the call is easy. When it is not, I make it anyway, own it, and adjust as things come in. A team waiting on certainty is a team losing time.

08

Run it and keep the standard

I build in the accountability so the decision survives contact with reality and the plan keeps working after I am gone.

What the approach comes down to

Evidence over assumptions.

I weigh the evidence before acting and flag a guess as a guess. That is most of what makes a recommendation worth trusting.

The inside shapes the outside.

How a company runs internally decides what it can deliver externally. Good marketing cannot compensate for broken operations, so I treat internal alignment as part of the strategy.

Build the system, not the one-off.

I solve the problem once and make the solution repeatable, so the next ten decisions do not start from scratch. And I keep the system as simple as the problem allows.

Decide when it is time.

Getting it right and deciding in time are not opposites. I do the work to earn the call, then I make it when waiting would cost more than it is worth.

The question I hold myself to

Could I explain this call in the open, on the evidence, with nothing hidden?

If yes, I move. If the honest answer depends on burying an inconvenient number, it is not ready, and I keep working until the decision can stand on its own. That is the standard behind the rest of this site.