Enterprise apps aren’t going anywhere (for a while). The doomsday articles are getting you keep scrolling but are missing the point of the new tech. The "App Gap" that vibe coding solves sits in the space between productivity apps and enterprise apps.

Enterprise apps are too embedded. Too many workflows, too many approvals, too many custom flows and dependencies. AI isn’t going to magically replace Salesforce, SAP, ServiceNow, Workday, Oracle, etc.

Introducing the "App Gap".

On one side, we’ve got the productivity tools we all live in: Sheets. Docs. Slides. Email. Calendar.

On the other side, we’ve got enterprise apps: Salesforce. Workday. Jira. Systems of record.

For the most common tasks, we buy enterprise systems.

For everything else, we shoe-horn the task into a productivity application.

Great Product Management skills are a combination of hard skills and soft skills. As technology gets easier to use, the soft skills actually get a little bit more important.

It’s the time of year where leaders in all organizations are planning for next year, creating an Annual Operation Plan (AOP).

While these plans may not always unfold exactly as envisioned, they create a shared understanding among leaders and teams about key priorities for the coming year.

I recently facilitated a roundtable with several leaders about annual planning and distilled the discussion into an approach that is less painful and more fruitful.

After a reorg, my team inherited what we thought was an awesome product.

We had big name clients and a flashy demo that opened door after door for new prospective clients.

However, as we talked to current clients and looked into their use of the product (or lack thereof), it was clear this product was struggling.

As CTO and Head of Product, I worried about the 13th month.

After an initial 12 month subscription, we wanted our clients to sign up for that 13th month, to renew for another year.

At PowerReviews, we had 1,200 clients in 20 countries. Every month, one or more client’s one year subscriptions were coming up for renewal.

A panel of industry execs weighed in on how we can get exec backing for design and research activities.

We discussed the role of UX research, the importance of qualitative and quantitative data, and how to demonstrate the value of design to non-design senior leaders.

Many companies adopt the Objectives and Key Results (OKRs) framework.

They create goals but struggle to achieve them.

Only some of this failure can be blamed on the goals themselves.

Part of this failure can be attributed to a lack of an analytic culture and a lack of an analytic mindset in your key employees.

It’s a simple question.

But often there’s an unsatisfying answer.

The first step towards understanding whether you're successful today starts with recognizing (and using less of) the following types of data: “Anecdata”, Reactive measurements, and Internal metrics.

“Start somewhere, anywhere.”

The first Product Discovery effort for a team doesn’t have to be perfect.

Product leaders don’t have to be experts in Product Discovery to get their teams started doing Product Discovery.

As a coach, I facilitate most every session that I attend. The group size ranges from 3 to 100 people. These are some of my top techniques for getting the most out of individuals in a group setting.

Use these techniques to avoid groupthink and one-sided discussions.

Launching a product feels like success.

I've launched hundreds of features and products and that feeling never gets old.

Sending this newsletter feels like a launch, providing a mini rush of positive emotions.

But I know better than that.