Over the years, I've used a wide range of Product Marketing frameworks, templates, and methodologies, many of them inspired by resources from Product Marketing Alliance and other Product Marketing practitioners.

While these frameworks provide useful structure, I've found that no project follows a template exactly.

Different products, teams, markets, and business contexts require different approaches.

What remains consistent is not the framework itself, but the way I approach the work.

Start with Understanding

Before building messaging, planning a launch, creating enablement materials, or developing a go-to-market strategy, I focus on understanding the context.

This usually means speaking with stakeholders, reviewing product information, understanding business objectives, exploring customer needs, and identifying the problem we're trying to solve.

The deliverable rarely matters if the underlying problem hasn't been properly understood.

Build Shared Understanding

Product Marketing sits at the intersection of multiple teams.

Product, Sales, Marketing, Customer Success, Support, and Leadership often view the same initiative from different perspectives.

One of the most important parts of my work is creating alignment before execution begins.

This can take many forms: stakeholder interviews, kickoff workshops, validation sessions, launch planning meetings, messaging reviews, or cross-functional checkpoints.

The objective is not consensus for the sake of consensus.

The objective is creating enough shared understanding for teams to move in the same direction.

Translate Complexity 

Much of my experience has been in technically complex environments.

Whether the challenge involves AI products, SaaS ecosystems, integrations, APIs, workflow automation, or enterprise software, the work often comes down to the same question:

How do we make something complex easier to understand without oversimplifying it?

This is where positioning, messaging, customer education, and narrative development become critical.

My goal is not to remove complexity.

It's to organize it in a way that makes sense to the people using, buying, supporting, or selling the product.

Design for Adoption

Creating a launch plan, messaging framework, or enablement asset is only part of the job.

The real challenge is ensuring that people actually use it.

That's why I place significant emphasis on adoption.

Whether it's a new product launch, a messaging initiative, or an internal process, I think carefully about how the work will be introduced, communicated, maintained, and embedded across teams.

Create Systems, Not Just Deliverables

Many Product Marketing projects produce outputs.

Launch plans.

Positioning documents.

Messaging frameworks.

Sales enablement materials.

These are important, but I tend to think beyond the immediate deliverable.

Whenever possible, I look for opportunities to create reusable processes, documentation structures, and operating mechanisms that can continue creating value long after a specific project has finished.

Because products evolve.

Teams change.

Organizations grow.

Good systems help navigate that complexity over time.