Jon Olson

[ESPN @espn]

TEXAS A&M WINS ITS FIRST-EVER VOLLEYBALL NATIONAL CHAMPIONSHIP IN SCHOOL HISTORY 🏆

[Juston Drake @JustonStrmRider]

5 inch hailstone @SimonStormRider and I measured in Johnson City, TX at approximately 7:50 PM CDT. @NWSSanAntonio

[Jason Fried @jasonfried]

The 37signals Guide to Internal Communication

The how, where, why, and when we communicate. Long form asynchronous? Real-time chat? In-person? Video? Verbal? Written? Via email? In Basecamp? How do we keep everyone in the loop without everyone getting tangled in everyone else’s business? It’s all in here.

Rules of thumb, and general philosophy

Below you’ll find a collection of general principles we try to keep in mind at 37signals when communicating with teammates, within departments, across the company, and with the public. They aren’t requirements, but they serve to create boundaries and shared practices to draw upon when we do the one thing that affects everything else we do: communicate.

1. You can not not communicate. Not discussing the elephant in the room is communicating. Few things are as important to study, practice, and perfect as clear communication.

2. Real-time sometimes, asynchronous most of the time.

3. Internal communication based on long-form writing, rather than a verbal tradition of meetings, speaking, and chatting, leads to a welcomed reduction in meetings, video conferences, calls, or other real-time opportunities to interrupt and be interrupted.

4. Give meaningful discussions a meaningful amount of time to develop and unfold. Rushing to judgement, or demanding immediate responses, only serves to increase the odds of poor decision making.

5. Meetings are the last resort, not the first option.

6. Writing solidifies, chat dissolves. Substantial decisions start and end with an exchange of complete thoughts, not one-line-at-a-time jousts. If it’s important, critical, or fundamental, write it up, don’t chat it down.

7. Speaking only helps who’s in the room, writing helps everyone. This includes people who couldn’t make it, or future employees who join years from now.

8. If your words can be perceived in different ways, they’ll be understood in the way which does the most harm.

9. Never expect or require someone to get back to you immediately unless it’s a true emergency. The expectation of immediate response is toxic.

10. If you have to repeat yourself, you weren’t clear enough the first time. However, if you’re talking about something brand new, you may have to repeat yourself for years before you’re heard. Pick your repeats wisely.

11. Poor communication creates more work.

12. Companies don’t have communication problems, they have miscommunication problems. The smaller the company, group, or team, the fewer opportunities for miscommunication.

13. Five people in a room for an hour isn’t a one hour meeting, it’s a five hour meeting. Be mindful of the tradeoffs.

14. Be proactive about “wait, what?” questions by providing factual context and spatial context. Factual are the things people also need to know. Spatial is where the communication happens (for example, if it’s about a specific to-do, discuss it right under the to-do, not somewhere else).

15. Communication shouldn’t require schedule synchronization. Calendars have nothing to do with communication. Writing, rather than speaking or meeting, is independent of schedule and far more direct.

16. “Now” is often the wrong time to say what just popped into your head. It’s better to let it filter it through the sieve of time. What’s left is the part worth saying.

17. Ask yourself if others will feel compelled to rush their response if you rush your approach.

18. The end of the day has a way of convincing you what you’ve done is good, but the next morning has a way of telling you the truth. If you aren’t sure, sleep on it before saying it.

19. If you want an answer, you have to ask a question. People typically have a lot to say, but they’ll volunteer little. Automatic questions on a regular schedule help people practice sharing, writing, and communicating.

20. Occasionally pick random words, sentences, or paragraphs and hit delete. Did it matter?

21. Urgency is overrated, ASAP is poison.

22. If something’s going to be difficult to hear or share, invite questions at the end. Ending without the invitation will lead to public silence but private conjecture. This is where rumors breed.

23. Where you put something, and what you call it, matters. When titling something, lead with the most important information. Keep in mind that many technical systems truncate long text or titles.

24. Write at the right time. Sharing something at 5pm may keep someone at work longer. You may have some spare time on a Sunday afternoon to write something, but putting it out there on Sunday may pull people back into work on the weekends. Early Monday morning communication may be buried by other things. There may not be a perfect time, but there’s certainly a wrong time. Keep that in mind when you hit send.

25. Great news delivered on the heels of bad news makes both bits worse. The bad news feels like it’s being buried, the good news feels like it’s being injected to change the mood. Be honest with each by giving them adequate space.

26. Time is on your side, rushing makes conversations worse.

27. Communication is lossy, especially verbal communication. Every hearsay hop adds static and chips at fidelity. Whenever possible, communicate directly with those you’re addressing rather than passing the message through intermediaries.

28. Ask if things are clear. Ask what you left out. Ask if there was anything someone was expecting that you didn’t cover. Address the gaps before they widen with time.

29. Consider where you put things. The right communication in the wrong place might as well not exist at all. When someone relies on search to find something it’s often because it wasn’t where they expected something to be.

30. Communication often interrupts, so good communication is often about saying the right thing at the right time in the right way with the fewest side effects.

[Jon Olson @Jdolson2010]

@johncutlefish @NotionHQ @coda_hq I am a Coda fanatic. I use it as a CRM, a prototyping tool and a strategic planning/communication tool. I have used Notion lightly but Coda has always felt focused more on automation/workflow/formula etc. on top of comparable content capabilities. Happy to demo if interested.

[Jon Olson @Jdolson2010]

@johncutlefish I think “Empowering” teams is focusing on enabling teams to be successful and making/supporting/investing in the continuous improvements to architecture, team structure, budgeting, information flows, etc. I feel that this needs leaders with that mindset.

[Jon Olson @Jdolson2010]

@iamireneyu I ran into https://t.co/awLanf1L0T a while back (markdown based interactive diagrams). It’s a great way for me to make sure I understood the dimensions of various workflows. It’s a bit cumbersome to get started with, but forces some extra logical thinking and modeling.

[Jon Olson @Jdolson2010]

@sambhigham Yes please

[Jon Olson @Jdolson2010]

@shreyas @ZevLapin I have felt that it makes sense to have that as a part of building the strategy. The strategy is the focused effort to move to that state. I feel it’s necessary to keep the two close and that the absence of one leads to a lack of success in the other.

[Nicole Daines @NicoleDaines]

Thinking about a #product leader’s ability to deliver impact at scale. 🧵

What would you add?

#productmanagement #productleadership

[Jon Olson @Jdolson2010]

@tobiasrogers My take: You're only as good as your influence.

While you get a benefit from your engineering team being incentivized to work with you, how you influence the other people that are needed to realize product success is very (equally?) important.

[Louie Bacaj @LBacaj]

I managed multiple engineering teams before quitting big tech.

Now that I quit, I can speak freely.

Here are 12 things your manager may not be telling you, but I know for a fact will help you. 👇

[Shreyas Doshi @shreyas]

Product Management—in 1 tweet.

Role:
Define the product & coordinate actions across the org to enable its success

Success:
User adoption
Business impact

Skills:
Common sense
Immense empathy
Influential communication

Traits:
Low ego
Deep care
High agency

Simple, but not easy.

[Sam @sambhigham]

The 10 of the most popular tweets from 10 of the best Product people I've found on Twitter.

Feat.
@shreyas
@johncutlefish
@simplybastow
@onejasonknight
@bfgmartin
@lennysan
@lissijean
@ttorres
@cagan

👇

[Jon Olson @Jdolson2010]

It's an exciting day at WorkForce Software! Learn more about the WorkForce Suite – and how we're redefining workforce management solutions to support the future of work for ALL workers. https://t.co/phKjbk1ocC

[mike morini @mikemorini77]

It's a big day at @WorkForceSW as we introduce the future of work for employees of every generation! Head to our website for more on this exciting announcement: https://t.co/qxseZc3OTI

[Joe Ross @josephrross]

Sustained agility is essential in these times of constant change, yet impossible without a highly engaged workforce. #makingworkeasy #innovation #employeeexperience https://t.co/q5E5h1ALeJ

[WorkForce Software, an ADP company @WorkForceSW]

Our Chief Product Officer is featured in The Times’ 2021 Employee Experience and Wellbeing Report! Get a free copy today to read his insights on prioritizing the #employeeexperience for sustained business success in the new workplace: https://t.co/7NRHZuA9C6

[Shreyas Doshi @shreyas]

Why product management is hard

(and why good product management matters)

1/15 👇🏾