Join 📚 Quinn's Highlights
A batch of the best highlights from what Quinn's read, .
DEEP Framework: Documenting Decisions, Events, Explanations, and Proposals in Your Org
Summary:
The DEEP framework emphasizes the documentation of decisions, urging the recording of the rationale behind business and general decisions.
It also stresses the importance of documenting events such as meetings and town halls, highlighting the need for summarization. Furthermore, the framework encourages documenting explanations, especially in the context of onboarding, as they often involve repeated material.
Lastly, it emphasizes documenting proposals or ideas, allowing individuals to present their rationale to others and providing time for considered reactions.
The acronym 'DEEP' serves as a reminder for teams to consider the documentation created within their workflow.
Transcript:
Speaker 1
So I came up with an acronym as well, and I call that acronym deep. I think you'll identify with some of these. So deep for decisions, if there's ever a decision, then you should record the rationale for it. And we've talked about it endlessly on our tech radar's decision record systems. But I extend that to business decisions as well and general decisions as well. So similar format. Then there's events. So you have a town hall, you have a meeting, all of those are events, right? And you better document them for the benefit of other people. And when I say document, I mean, summarize, sure, you can have a recording or snippets of recordings if they are useful for people, but the summary is the more important thing. Then there's explanations, and I found these very useful in the context of onboarding, because there's a lot of explainer material that gets repeated in onboarding. And those are definitely great candidates for documentation. And the last one is proposals. And I called that proposals, but really I'm trying to talk about things like ideas. So let's take an example. I want to use this new library on my project. I have a certain rationale for it. Let me write down the thought process. What value is it going to bring? Let me present it to everyone. Everyone has the time to consume it. Oftentimes we go into decision making with a lot of cognitive load, where, you know, Ken explains in rapid fire things that he's been thinking about for the last 15 days. And now I have to consume it in the next 30 minutes and give Ken a year or nay. It's really difficult because Ken's done all the deep thinking, I need the time to process it and writing gives me the time to process it, right? And I can also not give knee jerk reactions, but considered reactions. So proposals, and that starts to include design documentation, idea papers, any kinds of proposals that you make on the team. So that acronym deep is a good trigger for teams to kind of hold on to and think about what is the documentation we're creating in the flow of work.
Asynchronous Collaboration — Getting It Right
Thoughtworks Technology Podcast
Create a User Manual of Yourself for Others
Summary:
Creating a user manual for yourself, including strengths, weaknesses, triggers, blind spots, and insights for working effectively with you, enables others to understand and collaborate with you more easily.
By soliciting feedback from colleagues and using their input to enhance self-awareness, you can provide new team members with valuable insights about working with you, facilitating quicker and more effective collaboration.
Transcript:
Speaker 1
He said, you know, when i buy a new car, it comes with an owner's manual, so i know how to operate it. But when i work with a new person, whose way more complex than a car, i don't get anything. And so i'm kind of starting from square one, when fact, they have all these experiences that could teach me something from their past about how to work with them better in the present And the future. And so what he did, same as orschol nick, he sat down and he wrote up one pager on how to work with him effectively. What are his strength what are his weaknesses, what are the triggers that bring out the worst in him? What are the the moments that bring out in the best in him? And then he didn't stop therehe asked his team to write their user manual for him, so that he could gauge his own self awareness. And of course, he found the team's os is much more ecihtful and accurate than his own, because of the blind spot factor in part. But now every new person who works with him gets that one pager and gets to immediately start as if they'd known him for a month or two, and say, ok, you know, here are the things i might want To adapt if i want to be really affective with this nager. And so i've gone, i've gone and done that. I asked a bunch of people who worke with me to write my user manual. Andit is very simple. The questions are, what are my strengths? What brings those out? What are my weaknesses? What brings those out? What are my blind spots? And what do you know now about working with me that you wish you had known when we first started working?
#399 — Adam Grant — The Man Who Does Everything
The Tim Ferriss Show
Inversion: Avoiding stupidity is easier than trying to be brilliant. Instead of asking, “How can I help my company?” you should ask, “What’s hurting my company the most and how can I avoid it?” Identify obvious failure points, and steer clear of them.
50 Ideas That Changed My Life - David Perell
perell.com
...catch up on these, and many more highlights
Readwise