Think Out Loud

Greg Kogan

Apr 27, 2018 — 1 min read

After finding an issue related to an analytics product, I wrote an email to their support team asking for help. I described the observed issue, gave context, and speculated a cause. I hit send and went on with my da—wait, I just thought of another possible factor, and I should tell them. Send again.

Hold on… This could all be traced to this one thing; I should point them to it. Send.

Oh, let me see the revision history of that thing…

Ah, this must be it. Let’s try a fix…

Yes, that was it. I should tell them it’s resolved, and describe the fix in case they see this again. Send.

Maybe I could’ve figured it out without bugging the support team, but maybe not. Each time I transcribed my observations and thought process for them, it sparked another idea, and another, and finally it brought me to the solution.

Thinking out loud helps us see problems clearly. When there’s nobody nearby to talk to, find someone to write to.^[1]

If you’re on the receiving end of someone asking for help, don’t rush to respond; they might just find the answer if you let them think after the send.^[2]

[1] Or talk to a rubber duck.

[2] Thanks to the Segment support team for their patience.

After four years at Pinecone, I'm back to consulting

After helping Pinecone go from an unknown pre-seed company to a household name in the AI space, I'm returning to independent consulting (and writing). Mission-driven In 2013, the same year I started consulting, I got the idea to run the New York City marathon. That idea turned into

Removing stuff is never obvious yet often better

You know the nagging feeling that your product, project, or company has become more complicated than it needs to be? You can solve many problems and get better results by doing something unthinkable to many: removing parts that once seemed essential. My crusade against complexity continues with this short story

Would Anything (of Value) Be Lost?

“Wabl” is a principle I instill in my own and my team's work. (Pronounced like “wobble”.) I want to share it with you because it could help you do better work with less time and agony. When you review some work — like code, a strategy, an architecture, a

Being Swamped is Normal and Not Impressive

Being swamped — overwhelmed by stuff to do — is the default state of being within a startup. There's always more to do than time to do it, and the list keeps growing. Everyone else working at every other startup feels this too. Even if it doesn't look

Read more

After four years at Pinecone, I'm back to consulting

Removing stuff is never obvious yet often better

Would Anything (of Value) Be Lost?

Being Swamped is Normal and Not Impressive