A career can have a spine without fitting in a box

The useful thing about being a generalist is that I can keep following a problem after it crosses a departmental boundary.

A creator campaign may look like a marketing problem until the audience reaches a confusing purchase flow. A community may need more members, but the real gap could be weak programming or no reason to return. A new website may need better copy, while the deeper issue is that the offer, payment system, and operational promise do not agree.

I tend to enter through whichever door is open, then follow the work until the real constraint becomes visible.

That is the spine of my career.

I follow the problem one step further

At Gradly, I worked on growth for a product serving international students in the United States. Health insurance is not an easy impulse purchase. Students have university-specific requirements, waiver deadlines, unfamiliar terminology, and very reasonable doubts about whether a plan will actually work for them.

Creator and community partnerships could generate attention, but attention alone did not solve the trust problem. The work continued into content briefs, webinars, WhatsApp journeys, university-specific communication, purchase flows, product states, lifecycle messages, and attribution.

That changed the questions I asked.

Which creators had the audience’s trust? What did students need to understand before they could act? Where did the promise made in content become confusing inside the product? Could we connect a partnership to behaviour after the click through UTMs, PostHog, and flow tracking? What should we repeat, change, or stop?

The channel was only one part of the system. Growth depended on the relationships between the parts.

I look for the handoff where meaning gets lost

Many problems survive because each team completes its own piece correctly.

Content publishes the campaign. Design finishes the page. Product ships the flow. Operations handles the exceptions. Sales receives the lead. Nobody has done obviously bad work, but the customer still experiences one continuous journey, including every gap between those teams.

I am drawn to those gaps.

At Unshackled, the work around a paid immigration community stretched across the website, subscription journey, payment infrastructure, content, social distribution, newsletter publishing, and the operating rhythm behind them. Treating each as a separate deliverable would have produced separate improvements. Connecting them created a clearer path from discovering the community to understanding its value and becoming a paying member.

This is where range becomes practical. I can discuss positioning with a founder, map the path to purchase, work through content and distribution, examine the tooling, brief a specialist, and document the process without losing the original business question.

I do not need to be the deepest specialist in every room. I need enough understanding to recognise the dependency, bring in depth when it is required, and keep the whole outcome coherent.

Tools are part of the workbench

I have learned a slightly unreasonable number of tools because early-stage work rarely waits for the perfect team or setup.

Framer and Webflow help me move from a conversation to a working site. PostHog and UTMs help me see what happened after launch. Wati and OpenPhone make communication flows tangible. Fillout, Stripe, and Circle can turn an offer into an operating service. AI helps me research unfamiliar territory, test directions, troubleshoot, draft, prototype, and turn repeated judgment into reusable workflows.

The tool is rarely the point. I learn it because something is blocked.

Knowing how the machinery works also improves collaboration. I can write a more useful brief, understand what a designer or developer is pushing back on, spot an operational edge case, and avoid proposing ideas that collapse during implementation.

Ownership should leave a system behind

Going the extra mile is often described as personal effort: stay later, take on more, rescue the deadline.

I prefer a more durable version. Follow the consequence one step further, then make the next version easier.

If a creator partnership works, capture why it worked and build a process for sourcing, briefing, tracking, and reviewing the next one. If a campaign keeps stalling, find the missing decision or owner. If a founder has to explain the same standard repeatedly, turn that judgment into an SOP, template, or AI-assisted workflow. If the data cannot answer whether the work mattered, improve the measurement before producing more activity.

Ownership means staying close enough to the details to see the hidden problem, then building enough structure that the team does not need another heroic save.

Where I do my best work

I am most useful when the outcome matters more than the boundary around the role.

That usually means an early-stage team, a trust-heavy category, or a growth problem involving several moving parts: creators, partnerships, community, content, product, conversion, and operations.

Give me the intended outcome, the constraints, and the people affected. I will ask questions until the actual problem is clear, get close enough to the work to make progress, involve specialists where depth matters, and keep following the thread until someone or something can reliably own what comes next.

A title can describe where I enter the work. The spine is what I refuse to lose while moving through it.