In practice — questions, and the work behind them | Vinish Garg
Vinish Garg Framing
Products die because of lack of conversations. Let's have some.
Weuday Influence Timeline
Vinish Garg · In practice

We are all support functions. The foundation is at the intersections.

Curiosity. Framing. Incentives.

Teams—engineering, design, marketing, content, revenue, support, research. A product’s success does not lie with teams, it lies on the intersection of teams. Each team working as a support function of every other team is the most underrated force in product work. I have enabled it, and you can too.

It takes three things, and none of them is talent: people curious enough to look past their own part, someone willing to frame the question nobody has asked, and incentives that reward doing either. Find your intersections below.

Product intelligence
Product thinking
Product sense
Product systems

Start where you are

Pick the one that sounds like you. You'll get my read on where it comes from, the questions I would ask, and the work behind it.

I mean it. Spend the day with people who would notice you being there. Reading is not the win, and I have written about why.
On “{{ activeScenario.prompt }}”

{{ activeScenario.take }}

Then ask your team
{{ q.n }} {{ q.q }}
I have been saying this a while

{{ activeScenario.quoteText }}

{{ activeScenario.quoteMeta }} See the post →

From here, you have two options.

  • —highlighted at the top of the library below.
  • —not quite your situation? Type the question you actually have.
You asked: “{{ askAnswer.question }}”
{{ askAnswer.label }}

{{ askAnswer.take }}

{{ askAnswer.countText }}
If your situation is more specific than this, that's a conversation—ask me directly →
Ask in your own words. See matching cards in the library, or I will let you know that there is no matching reference for you.
Try

The library

{{ lens.label }}
{{ resultNote.text }}

{{ emptyState.text }}
{{ item.facetLabel }} ★ {{ item.source }}

{{ item.title }}

{{ mp.t }}

{{ item.matchLabel }} Open →

Reading helps. Working with someone who has been doing it is another experience.

This is how I consult →
Another way in

Not sure what to call it yet?

Start from what you can feel rather than what you can name. Pick the condition, then the reading that sounds closest.

{{ reframe.symptom }}

{{ reframe.prompt }}
What I would call this

{{ reframe.answer.name }}

{{ reframe.answer.take }}

Ask your team

{{ reframe.answer.ask }}

Someone else says it well

{{ reframe.answer.source }}
Where I have written about it
What I would call this

Pick a reading and I will give the thing a name.

A name you can take into the room, plus where I have written about it.