Tags
Writing, research, projects, and photos around “Product Thinking”.
A consultation about a high-pressure blended role: looking past the schedule to the business goal, shared expectations, resources, and authority the work requires.
Consulting
7 min read
Part of the column “Engineering Teams & Technical Judgment” · Chapter 1
An edited consultation about an FDE conference, technical communication, and AI’s business value: when owners care about revenue and cost, how can technical people explain their work as a result worth testing?
Consulting
9 min read
Part of the column “Consulting & B2B Business” · Chapter 1
Business Model Canvas explained through nine questions: what each box answers, how the pieces fit together, and why a project's needs change across company stages.
Method
5 min read
A note on a distinction: the business model canvas is 'made for yourself,' the startup pitch is 'told to others,' and investor due diligence is 'others scrutinizing you'; the three differ completely in purpose, focus, and framing — don't mix them up.
Method
5 min read
Good collaboration is built on trust, shared information, and solving problems together; when goals conflict, don't make promises privately—escalate with complete information to align.
Short
2 min read
Technology can't manufacture a selling point out of thin air, but engineers can still help the team understand users more precisely, shorten validation cycles, and turn implicit constraints into choosable problems.
Short
2 min read
When entering an unfamiliar business or system, don't rush to start from a local solution. First map the users, the process, inputs and outputs, key constraints, and value, so you know what to ask.
Short
2 min read
Product sense isn't guessing at requirements. A ready-to-use list of talking points, from two angles: how engineers should understand the product, and what product managers actually do.
Short
2 min read
Part of the column “One-on-One Conversations” · Chapter 6
From completing requirements to taking part in planning, how engineers place technical implementation between user problems and business outcomes.
Short
13 min read
Part of the column “Product Judgment” · Chapter 1
The job of a product overview is not to collect as many facts as possible, but to help readers build a shared question, form judgments, and understand what evidence is still missing within a limited time.
Short
7 min read
Part of the column “Product Judgment” · Chapter 2
Self-use isn't about 'spending more time in the product'; it's a feedback system spanning real tasks, valid evidence, and verified fixes.
Short
4 min read