Latest / How I Work / BONUS: Have we got work all wrong? Modern work principles with Almanac CEO Adam Nathan
Transcript
- 0:00Speaker 1: Do you remember when working from home was a rarity.
- 0:05Speaker 1: Maybe you knew a couple of contractors who had a
- 0:07Speaker 1: home office, or you'd heard of a few companies with
- 0:10Speaker 1: pretty flexible working arrangements.
- 0:13Speaker 2: Then all of a sudden, it seemed like almost.
- 0:16Speaker 1: Everyone started working from home thanks to the pandemic, and
- 0:21Speaker 1: things changed for good when we all realized we could
- 0:25Speaker 1: get by with things like Zoom and Google Docs. But
- 0:29Speaker 1: what if we were wrong. Adam Nathan is the co
- 0:34Speaker 1: founder and CEO of Almanac, which has structured collaboration software
- 0:39Speaker 1: for remote teams, and he's worried that where we work
- 0:44Speaker 1: has changed, but how we work hasn't. So what needs
- 0:50Speaker 1: to change? Well, it all starts with Almanac's principles of
- 0:55Speaker 1: modern work. My name is doctor amanthe Immer. I'm an
- 1:04Speaker 1: organizational psychologist and the founder of behavioral science consultancy Inventium,
- 1:09Speaker 1: And this is how I work a show about how
- 1:12Speaker 1: to help you do your best work. So if you
- 1:16Speaker 1: visit almanex website. As well as learning all about the software,
- 1:21Speaker 1: there is a whole section dedicated to Adam and his
- 1:25Speaker 1: team's thinking about how teams and especially teams that don't
- 1:29Speaker 1: work in the same location. Five days a week, can
- 1:32Speaker 1: think differently and a whole lot better about work. And
- 1:36Speaker 1: I was keen to know why did Adam even create
- 1:40Speaker 1: these principles in the first place.
- 1:43Speaker 3: We started the company off the pretty simple thesis that
- 1:46Speaker 3: where we work has changed, but how we work hasn't.
- 1:49Speaker 3: And I think anyone who's lived through the past three
- 1:51Speaker 3: or four years knows what I mean. But just to
- 1:53Speaker 3: put some data on it, before the pandemic, about twenty
- 1:57Speaker 3: two percent of of these white color professionals in the
- 1:59Speaker 3: United States worked remotely or in some kind of distributed
- 2:02Speaker 3: context to the numbers closer to seventy percent, so you're
- 2:05Speaker 3: seeing something like a four or five x increase in
- 2:08Speaker 3: remote work. And the number has actually grown since the
- 2:11Speaker 3: end of the pandemic. And you know, I don't love
- 2:13Speaker 3: the I don't love the phrase remote work. I'd rather
- 2:16Speaker 3: call it internet work, because what I think is really
- 2:18Speaker 3: happening here is this broader shift from working in the
- 2:21Speaker 3: office to working on the Internet. And this has happened
- 2:23Speaker 3: in phases over time. Even before the pandemic, A lot
- 2:25Speaker 3: of people, even if they went into an office, were
- 2:27Speaker 3: working in Google Docs, communicating on Slack, meeting on Zoom.
- 2:32Speaker 3: A lot of large companies were distributed. Before was cool
- 2:35Speaker 3: because they had offices across different cities and even countries,
- 2:40Speaker 3: but remote work. The pandemic was really a one way
- 2:45Speaker 3: door into remote work for a lot of people, and
- 2:47Speaker 3: it was obviously a surprise, and overnight people couldn't go
- 2:50Speaker 3: into their offices anymore. And it turns out that, you know,
- 2:52Speaker 3: we could kind of get by at work with the
- 2:54Speaker 3: basics of creating and collaborating with the tools that we had.
- 2:57Speaker 3: But what happened also during the pandemic was that indicators
- 3:01Speaker 3: around things like burnout and job satisfaction and management efficiency
- 3:05Speaker 3: started blinking red because we were still all working online
- 3:11Speaker 3: as if we were in an office from nine to
- 3:13Speaker 3: five in the same place. So meetings and messages started
- 3:16Speaker 3: to become overused as tools of getting stuff done. When
- 3:20Speaker 3: people can't be around their colleagues anymore, things like trust
- 3:23Speaker 3: and connections started to decrease precipitously, and so people started
- 3:28Speaker 3: to burn out at work and become very dissatisfied and
- 3:32Speaker 3: doubt even when before the pandemic that wasn't happening. And
- 3:37Speaker 3: we think the root cause at Almanac is that we've
- 3:40Speaker 3: now changed where we work, but we haven't actually evolved
- 3:44Speaker 3: yet how we work, and so this mismatch between kind
- 3:47Speaker 3: of the context in which we now all work and
- 3:49Speaker 3: live and the way that we're doing our jobs is
- 3:51Speaker 3: causing a lot of pain and frustration, to the extent
- 3:54Speaker 3: that some people quit their jobs or take themselves out
- 3:57Speaker 3: of their workforce, which is obviously not good for them,
- 4:00Speaker 3: also not good for our economy. It's not good for businesses.
- 4:03Speaker 3: There's actually been a slowdown in innovation over the last
- 4:06Speaker 3: twenty years, where a lot of the growth we're seeing
- 4:08Speaker 3: today is actually a byproduct of fundamental innovation that was
- 4:12Speaker 3: created before nineteen seventy. And so I think in order
- 4:16Speaker 3: to keep keep our planet spinning and making sure that
- 4:19Speaker 3: we're solving our greatest challenges and reaping our biggest opportunities,
- 4:22Speaker 3: that requires great collaboration and requires teams to work well,
- 4:26Speaker 3: and that means we need to figure out how to
- 4:27Speaker 3: work together in this new normal. And so when we
- 4:31Speaker 3: started the company, we weren't just trying to build a
- 4:34Speaker 3: better tool. In fact, there's I think nothing wrong with
- 4:38Speaker 3: document editors like Microsoft Word or Google Docs. It's more
- 4:41Speaker 3: that people are trying to use a tool that was
- 4:44Speaker 3: designed for a different world.
- 4:46Speaker 4: For something entirely different, and what.
- 4:48Speaker 3: We think people really need is a different way of working,
- 4:51Speaker 3: not just a different tool. And so when we started
- 4:53Speaker 3: the company, we didn't just sit down and start coding
- 4:57Speaker 3: away based on philosophy found and other products. We we
- 5:00Speaker 3: went first to talk to the best teams on the Internet,
- 5:02Speaker 3: people at companies like Amazon and Apple and Netflix and
- 5:07Speaker 3: get Lab and do is to understand, like how they
- 5:10Speaker 3: were working so well In many of these cases, they
- 5:12Speaker 3: figured out how to optimize their processes, their management styles,
- 5:16Speaker 3: their norms for the Internet way before the rest of
- 5:18Speaker 3: us did. And so we've done over five thousand interviews
- 5:21Speaker 3: at this point with people from these super high performing
- 5:23Speaker 3: teams to understand, like, how did you figure out how
- 5:27Speaker 3: to work? What was the initial insight, how's that evolved
- 5:31Speaker 3: into a best practice, And what we did from there
- 5:33Speaker 3: was kind of abstract away from specific instances to broad
- 5:37Speaker 3: generalizable principles that anybody can use, regardless of their company
- 5:41Speaker 3: or context to work faster on the Internet.
- 5:44Speaker 2: That's amazing.
- 5:45Speaker 1: Love the I love the depth that and the research
- 5:49Speaker 1: that went into creating these modern work principles. I've read
- 5:53Speaker 1: through them all and you know what else, Preparing for
- 5:56Speaker 1: this interview. I thought, I'll just I'll pick out my favorites,
- 5:59Speaker 1: but really down most of them because most of them
- 6:01Speaker 1: are my favorites. So I want to go through a
- 6:03Speaker 1: few of them because what I'm really interested in is
- 6:06Speaker 1: what does that look like in practice. So let's take
- 6:08Speaker 1: principle two, which says the best managers focus on outputs
- 6:12Speaker 1: and outcomes instead of hours worked or messages sent. So
- 6:16Speaker 1: I don't think you get much argument from you know,
- 6:19Speaker 1: forward thinking leaders about that. I feel like a lot
- 6:22Speaker 1: of leaders and managers say, you know, it has to
- 6:25Speaker 1: be about outcomes and not hours, but they don't necessarily
- 6:29Speaker 1: behave in that way when they're, say, evaluating their staff.
- 6:35Speaker 1: So I want to know, how do you do this
- 6:37Speaker 1: practically speaking.
- 6:39Speaker 3: Yeah, it's a great question. And just for some context here,
- 6:42Speaker 3: if you think about historical management theory, modern management really
- 6:47Speaker 3: came about with the advent of the modern factory in
- 6:49Speaker 3: the nineteen thirties and forties, and the job of a
- 6:51Speaker 3: manager there was to measure outputs, and the outputs in
- 6:54Speaker 3: this case it was like stuff coming off the factory line,
- 6:56Speaker 3: and so managers could set above the factory floor and
- 6:59Speaker 3: you know, look at like reports essentially of outputs and
- 7:03Speaker 3: see how the factory was performing. And in that case,
- 7:05Speaker 3: workers were kind of like cognitive machine, you know, they
- 7:07Speaker 3: were sorting stuff and doing specific, single oriented jobs, and
- 7:10Speaker 3: so management was I'm sure it wasn't simple then, but
- 7:15Speaker 3: it was pretty straightforward. As work a lot of work
- 7:19Speaker 3: moved from blue collar work to white collar work, from
- 7:21Speaker 3: kind of factory work to creative work. You couldn't see
- 7:24Speaker 3: the output of individual employees anymore. In many cases they
- 7:28Speaker 3: were complex or creative, and so the job of a
- 7:30Speaker 3: manager short to evolve to managing presence, which is to say,
- 7:34Speaker 3: did the employee show up at a specific time, were
- 7:37Speaker 3: they in the office to another time, did they attend meetings?
- 7:40Speaker 3: Even things like how good of a communicator are they?
- 7:43Speaker 3: How good are they appearing to collaborate, And a lot
- 7:46Speaker 3: of that I think has been kind of parodied and
- 7:48Speaker 3: reviled in modern media around kind of how a name
- 7:51Speaker 3: that is because even in the office, just because you
- 7:54Speaker 3: showed up wasn't necessarily correlated to whether you were doing.
- 7:57Speaker 4: A good job.
- 7:57Speaker 3: But it gave managers the same kind of control I
- 8:00Speaker 3: think as standing above a factory floor used to and
- 8:04Speaker 3: now in modern world where we're not in the same place.
- 8:07Speaker 3: At the same time, we've removed the ability for managers
- 8:10Speaker 3: to manage my presence, which I think is a good
- 8:12Speaker 3: thing because it allows us to fill it in with
- 8:13Speaker 3: something better. But to your question, how do we give
- 8:16Speaker 3: managers tools to actually manage outcomes rather than just presence?
- 8:22Speaker 3: And I think the key to the inser comes down
- 8:25Speaker 3: to transparency. And so if you think kind of about
- 8:28Speaker 3: a spectrum, in order to get to outcomes, you first
- 8:31Speaker 3: have to measure outputs, because somebody can't be doing a
- 8:34Speaker 3: good job if they're doing no job at all. And
- 8:36Speaker 3: so I think the core form of this is to
- 8:39Speaker 3: actually just look at tasks. So of the things I've
- 8:42Speaker 3: asked you to do, did you actually do them? If
- 8:45Speaker 3: you haven't done them, there's no way that you did
- 8:46Speaker 3: any job at all. You could do a good or
- 8:48Speaker 3: bad job, you've done nothing. And so creating transparency around
- 8:52Speaker 3: kind of the basic collaborative tasks that people do every day,
- 8:55Speaker 3: I think is the foundation to starting to measure outputs
- 8:57Speaker 3: and outcomes instead of things like presence. And so in
- 9:00Speaker 3: our tool in Almanac, we have a concept call request,
- 9:04Speaker 3: where you can ask someone for feedback or approval or
- 9:07Speaker 3: to complete something, or even just to read a document.
- 9:10Speaker 3: And this is really similar about how software engineers have
- 9:12Speaker 3: been working largely asynchronously for twenty years, where even when
- 9:16Speaker 3: they're on the same place as software engineer, through tools
- 9:18Speaker 3: that GitHub can ask another engineer to review their code
- 9:21Speaker 3: or approve something. And in gethub there's basically like a
- 9:24Speaker 3: lot like an activity feed from Facebook where you can
- 9:26Speaker 3: actually see did the person first like see my request,
- 9:29Speaker 3: kind of like a red receipt in I message, You know,
- 9:33Speaker 3: have they looked at it? What comments have they made
- 9:35Speaker 3: that they're attached to the request, what metafeedback have they given?
- 9:38Speaker 3: And so there's a lot of clarity around like where
- 9:41Speaker 3: the request is in process. And if you think about
- 9:44Speaker 3: like even basic task management tools from the office culture era,
- 9:48Speaker 3: you may ask somebody in an office to do something,
- 9:50Speaker 3: but even then you really have any clarity like where
- 9:53Speaker 3: is this work with Susan you know, digjo complete the task?
- 9:56Speaker 3: And so I think for managers to start to manage
- 9:59Speaker 3: by outcomes, you have to just understand is your team
- 10:03Speaker 3: doing the things you ask them to do, and that
- 10:06Speaker 3: starts to get you a sense of kind of quantity
- 10:08Speaker 3: of output, and then you can start to layer on
- 10:11Speaker 3: quality and I think ways to measure that are to
- 10:13Speaker 3: look at again through transparency of analytics. What was how
- 10:19Speaker 3: many comments did people put on their work? How many
- 10:22Speaker 3: comments did they put in other people's work? How do
- 10:24Speaker 3: you did people react to those comments? Where their threads?
- 10:26Speaker 3: Where they're things like reactions. If you think about kind
- 10:29Speaker 3: of the consumer world as a parallel for enterprise, if
- 10:32Speaker 3: you go on Twitter or Facebook or Instagram, you can
- 10:34Speaker 3: generally tell the quality of a post by the amount
- 10:36Speaker 3: of reactions. It's getting the number of likes, amount of comments,
- 10:38Speaker 3: that engagement in other words, and I think starting to
- 10:41Speaker 3: apply a lot of the same principles to enterprise collaboration
- 10:45Speaker 3: on comments and tasks and reviews and then aggregating those
- 10:49Speaker 3: analytically so that a manager can see how did Adam actually.
- 10:52Speaker 4: Do this week?
- 10:53Speaker 3: Did he complete his tasks? Did people think they were good?
- 10:56Speaker 3: Was he responsive to what other people on the team need?
- 10:58Speaker 3: You can start to get a picture of kind of
- 11:00Speaker 3: quality and quality of output.
- 11:03Speaker 4: By individual, and.
- 11:04Speaker 3: That starts to get managers the tools they need to
- 11:07Speaker 3: understand is the team doing their jobs?
- 11:10Speaker 4: Is the team moving the needle?
- 11:12Speaker 3: And that I think in the end builds trust and
- 11:14Speaker 3: a sense of connection between managers and their teams, because
- 11:18Speaker 3: even if they're not in the same room, the managers
- 11:19Speaker 3: a sense of is the ball moving forward, who's contributing
- 11:23Speaker 3: to the work, who's falling behind? And I think that
- 11:25Speaker 3: lack of that lack of trust that exist today for
- 11:28Speaker 3: a lot of teams comes from a lack of transparency.
- 11:31Speaker 1: It's interesting, like the distinction between outputs and outcomes. And
- 11:37Speaker 1: I know at Almanac you use okay as so objectives
- 11:42Speaker 1: and kre results.
- 11:43Speaker 2: That's correct, isn't it, Adam, we built.
- 11:45Speaker 3: Our own system because I think cars can be kind
- 11:48Speaker 3: of like a dark art or for a lot of
- 11:52Speaker 3: teams where they're actually quite I think they take a
- 11:55Speaker 3: lot of work to implement, and many teams don't do
- 11:57Speaker 3: them very well. So we've actually designed our own system Almanac,
- 12:01Speaker 3: that's largely based on setting a strategy every quarter, translating
- 12:06Speaker 3: that down into goals per month than to goals per week,
- 12:09Speaker 3: so that everybody understands how we plan to get to
- 12:13Speaker 3: the long term place we want to go, and then
- 12:15Speaker 3: having individuals in their work streams list their own goals
- 12:20Speaker 3: for the week in a public document and at the
- 12:22Speaker 3: end of the week grade themselves and if they.
- 12:23Speaker 4: Got that work done.
- 12:25Speaker 3: And so on this output point I was talking about before,
- 12:27Speaker 3: understanding like did you do the thing you said you
- 12:29Speaker 3: were going to do. We built a system at Almanac
- 12:32Speaker 3: largely based around these weekly tasks just to understand like
- 12:36Speaker 3: are people doing their jobs? And you know there are cases,
- 12:39Speaker 3: of course where people are doing their work but it's
- 12:41Speaker 3: not very good. But there's a very strong correlation between
- 12:44Speaker 3: people who aren't completing their task and people who aren't
- 12:47Speaker 3: producing outcomes in other words, moving the needle on an
- 12:51Speaker 3: important project.
- 12:52Speaker 1: The outcomes almost like the quality and outputs sort of
- 12:59Speaker 1: the quantity.
- 13:00Speaker 2: Is that simplifying it too much?
- 13:02Speaker 3: It's basically it's about impact on the spectrum. And so
- 13:06Speaker 3: outputs I think of as a.
- 13:09Speaker 4: As something that happens as a direct result of your activity.
- 13:12Speaker 4: And so if.
- 13:16Speaker 3: Let's say we're playing a sport and we're playing baseball,
- 13:19Speaker 3: and output is you know, the number of times that
- 13:22Speaker 3: I am batting and I swing and I connect with
- 13:25Speaker 3: the ball. You know, it's a verifiable activity where my
- 13:28Speaker 3: action led to a direct result.
- 13:30Speaker 4: Everybody can see it. It's pretty easy to measure.
- 13:33Speaker 3: Whether or not I'm hitting the ball, how is how
- 13:35Speaker 3: how much is that correlated with my team winning the game.
- 13:39Speaker 3: Who knows, Probably not that much I think about an
- 13:41Speaker 3: outcome though, as my team winning the game. You know,
- 13:45Speaker 3: it's it's something that happens that I'm contributing to, but
- 13:47Speaker 3: it's not a direct result of my activity. And so
- 13:51Speaker 3: out outcomes for businesses are things like we want to
- 13:54Speaker 3: grow this quarter, or we want to improve profitability, or
- 13:57Speaker 3: we want to produce new products. An output might be
- 14:00Speaker 3: if I'm an engineer, you know how many lines of
- 14:02Speaker 3: code I've written, if I've completed a feature. If I'm
- 14:05Speaker 3: a marketer, you know how many ads I've released or
- 14:08Speaker 3: how many lines, how many.
- 14:09Speaker 4: New tweets I've sent.
- 14:11Speaker 3: If I'm a you know, salesperson, it's the number of
- 14:14Speaker 3: calls I've made or number of demos I've booked, just
- 14:16Speaker 3: because I've you know, done it. A bunch of demos
- 14:18Speaker 3: doesn't necessarily mean that the company will grow, but they
- 14:20Speaker 3: are correlated, and so there's this relationship between the work
- 14:23Speaker 3: that I'm doing, how much of it I do, the
- 14:25Speaker 3: quality that I do it at, and the long term
- 14:29Speaker 3: goal of the company that many people are contributing to
- 14:31Speaker 3: that is also affected by outside factors, and so outcomes
- 14:36Speaker 3: are often what companies say their goals are and the
- 14:39Speaker 3: trick is how you tie that to the actual work
- 14:41Speaker 3: people are doing every single day.
- 14:43Speaker 1: And so is what you're saying that the goals that
- 14:47Speaker 1: individuals are setting, they're the outputs. And then the ladder
- 14:51Speaker 1: up to company outcomes. Yes, okay interesting, and so in
- 14:56Speaker 1: the language of okay as the output, So it's the
- 15:00Speaker 1: key results, like the quantifiable, measurable things that the people
- 15:04Speaker 1: are ultimately assessed on.
- 15:06Speaker 4: Yeah.
- 15:06Speaker 3: So in okay, our's okay stands for objectives and key results.
- 15:10Speaker 3: An objective is kind of a qualitative, big idea, something like,
- 15:13Speaker 3: you know, this quarter, we'd like to grow the business,
- 15:17Speaker 3: and a key result is attached to that objective. That's
- 15:19Speaker 3: a quantifiable metric that will help the team understand if
- 15:22Speaker 3: they achieve that objective. So if our goal is to grow,
- 15:25Speaker 3: if our objective is to grow the business, a key
- 15:27Speaker 3: result might be, you know, revenue increases fifty percent within
- 15:30Speaker 3: three months, and so you're measuring the key results to
- 15:33Speaker 3: understand if you've reached the objective.
- 15:36Speaker 4: And then those often ladder down.
- 15:38Speaker 3: If that's, for example, a company goal, those could ladder
- 15:40Speaker 3: down to team goals. So the product team is thinking
- 15:43Speaker 3: about how do we build new features. The sales team
- 15:45Speaker 3: is thinking about how to we sell those features. Marketing
- 15:47Speaker 3: team is thinking about how to we increase top of
- 15:49Speaker 3: funnel awareness, and that can lead it on even further
- 15:51Speaker 3: to individuals objectives and key results. So the system is
- 15:55Speaker 3: meant to scale from what a company sets all the
- 15:58Speaker 3: way down to what individual are doing every day, so
- 16:02Speaker 3: that there's broad alignment and clarity through the organization.
- 16:06Speaker 1: One of my other favorite principles, As I said, they're
- 16:09Speaker 1: all kind of favorites, but I really like this one
- 16:11Speaker 1: principle seeks collaboration should always start with a document instead
- 16:15Speaker 1: of a mating and I feel that that is completely
- 16:19Speaker 1: conjurary to how most organizations run things. So can you
- 16:25Speaker 1: tell me, if it starts with a document, what does
- 16:28Speaker 1: that document look like.
- 16:30Speaker 3: That's a great question, and I agree with you that
- 16:33Speaker 3: it sounds simple write everything down, but it's very unintuitive
- 16:37Speaker 3: to a lot of people and not often followed in
- 16:40Speaker 3: practice in terms of what to write down. I think
- 16:44Speaker 3: the best practice here is to use templates. And so
- 16:46Speaker 3: if you think about every document, not as a lot
- 16:50Speaker 3: of people do, as kind of a place to store,
- 16:52Speaker 3: like a final version of a contract or an agreement
- 16:55Speaker 3: something that happens at the end of a largely informal
- 16:57Speaker 3: process that's being conducted in meetings, but really as the
- 17:00Speaker 3: process itself, as the place where you write down the
- 17:03Speaker 3: initial idea, where you get feedback on it, where you
- 17:06Speaker 3: get formal approval, where you then distribute it as knowledge
- 17:09Speaker 3: to the rest of the team, even something that then
- 17:11Speaker 3: gets updated over time into future versions. The document isn't
- 17:15Speaker 3: just kind of like a piece of paper that goes
- 17:17Speaker 3: in a filing cabinet, as we used to regard them,
- 17:19Speaker 3: but really as the core collaborative surface for the team.
- 17:22Speaker 3: And so the best way to kind of codify a
- 17:25Speaker 3: process so that people follow it is to use a template.
- 17:28Speaker 3: And so I think the best practice here is to
- 17:30Speaker 3: have document templates for different types of processes. So, for example,
- 17:34Speaker 3: a PRD is a great template es for creating and
- 17:39Speaker 3: aligning as a team on product requirements for a new feature.
- 17:42Speaker 3: Using a sales template is essentially a form of starting
- 17:48Speaker 3: a process where you go through negotiation with a potential customer,
- 17:51Speaker 3: agree on terms, get them to sign it, and then
- 17:54Speaker 3: distribute it.
- 17:55Speaker 4: And so.
- 17:57Speaker 3: The simple but hard answer is that creating good templates
- 18:01Speaker 3: for the key processes that your company is doing is
- 18:06Speaker 3: the best way to make sure that those processes begin
- 18:10Speaker 3: with a document rather than a meeting, And by starting
- 18:13Speaker 3: with basically like a plug and play document, you can
- 18:17Speaker 3: actually not just reduce the number of meetings, but reduce
- 18:20Speaker 3: the amount of hours you're spending on the work, because
- 18:22Speaker 3: most of what companies are doing every day aren't like
- 18:25Speaker 3: totally new creative processes. Even if the point of a
- 18:29Speaker 3: process is to come up with a creative idea, the
- 18:31Speaker 3: process itself is often codified and structured in some ways,
- 18:34Speaker 3: and what a lot of companies are spending time doing
- 18:36Speaker 3: is reinventing the wheel on the process itself, and templates
- 18:39Speaker 3: are a great way to prevent that from happening.
- 18:45Speaker 1: We will be back with Adam soon where we talk
- 18:48Speaker 1: about what actually deserves a meeting at Almanac and what
- 18:53Speaker 1: is best done asynchronously. If you're looking for more tips
- 18:57Speaker 1: to improve the way that you work, I write a
- 19:00Speaker 1: short fortnightly newsletter that contains three cool things that I've
- 19:03Speaker 1: discovered that helped me work better, ranging from software and
- 19:07Speaker 1: gadgets that I'm loving through the interesting research findings. You
- 19:11Speaker 1: can sign up for that at Howiwork dot code. That's
- 19:14Speaker 1: how I work dot co so at almanac, what deserves
- 19:19Speaker 1: a meeting?
- 19:21Speaker 3: Yeah, I think there's two types of meetings that I
- 19:24Speaker 3: have found really valuable. One type of meeting that we
- 19:26Speaker 3: have often that I think is worth the time is
- 19:29Speaker 3: when we have a problem to solve that is a
- 19:32Speaker 3: complex problem that has a complex answer, where you can't
- 19:35Speaker 3: just send a document to somebody and say.
- 19:37Speaker 4: Do you approve or not?
- 19:39Speaker 3: And to be clear, there are a lot of processes
- 19:42Speaker 3: where there are simple answers to simple questions that can
- 19:45Speaker 3: be automated and completed asynchronously. And so you know, things
- 19:49Speaker 3: like approving marketing copy or redlining contracts or getting feedback
- 19:55Speaker 3: on new product proposals. Those are all things we don't
- 19:57Speaker 3: have meetings for out HAMANAC. But when we're for example,
- 20:02Speaker 3: trying to figure out, you know, what's our approach to
- 20:04Speaker 3: AI or what should our growth goal be this month,
- 20:09Speaker 3: those aren't things that are easily done asynchronously. They often
- 20:12Speaker 3: require lots of input from diverse stakeholders, a bit of
- 20:16Speaker 3: conversation where I think the conversation can lead to a
- 20:19Speaker 3: better outcome or answer than we could ever get to
- 20:22Speaker 3: if we were just communicating linearly. And for example, a
- 20:25Speaker 3: comments thread. So those types of complex problems with complex answers,
- 20:28Speaker 3: I think require a meeting. I think a second type
- 20:32Speaker 3: of meaning that we have that's helpful as something that's urgent,
- 20:36Speaker 3: where you actually just need to get something done now,
- 20:39Speaker 3: and that's where often people are in slack or another
- 20:44Speaker 3: communication channel and we're just getting on the phone can
- 20:46Speaker 3: actually get to an answer faster. And the third important
- 20:49Speaker 3: type of meaning is to create a sense of connection
- 20:53Speaker 3: and reinforce the culture of our team. And that's less
- 20:56Speaker 3: from like we have a business objective to complete and
- 20:59Speaker 3: more we're a bunch of humans working together every day
- 21:03Speaker 3: and spending a majority of our waking hours together and
- 21:06Speaker 3: recognizing that we are people and that we need to
- 21:09Speaker 3: connect with each other. And part of the joy of
- 21:13Speaker 3: work is working with is getting to spend time with
- 21:16Speaker 3: people that you like and respect and trust. And I
- 21:18Speaker 3: think a great way to reinforce that is their meetings,
- 21:20Speaker 3: where you get just so much more information by seeing
- 21:23Speaker 3: somebody their body language, how they react to what you're saying.
- 21:26Speaker 4: And we actually spend a lot of time.
- 21:28Speaker 3: In our kind of weekly or even daily stand ups
- 21:32Speaker 3: starting with a kickoff question. We have a whole library
- 21:35Speaker 3: of them at this point, like a thousand questions that
- 21:37Speaker 3: we figured out over time, things like what did you
- 21:39Speaker 3: want to be when you grow up?
- 21:40Speaker 4: Or what you're perfect Saturday? Or you know, what do
- 21:43Speaker 4: you serve.
- 21:44Speaker 3: On Christmas Evening? That help people understand more like who
- 21:50Speaker 3: they're really working with, because we're all so much more
- 21:53Speaker 3: than our jobs, and I think spending synchronous time to
- 21:56Speaker 3: get to know each other and build culture ultimately leads
- 21:59Speaker 3: to better work, more satisfied teams, and faster business value.
- 22:06Speaker 1: I want to talk about principal seven, which is the
- 22:09Speaker 1: more you ask for feedback, the better your end work
- 22:12Speaker 1: will be. I've got a few questions around that. Firstly,
- 22:17Speaker 1: when do you ask for feedback at what point in
- 22:20Speaker 1: a project?
- 22:21Speaker 4: All the time?
- 22:22Speaker 3: And we've learned as the principle has gone it and
- 22:27Speaker 3: we should have learned this sooner, judging from all the
- 22:31Speaker 3: research you've done where people talked about the importance of
- 22:33Speaker 3: feedback that you know, essentially, you know, if you think
- 22:38Speaker 3: about I think one a lot of the universes, compounding
- 22:42Speaker 3: that progress over time becomes greater and greater because you're
- 22:45Speaker 3: actually just building on the progress of the past, and
- 22:48Speaker 3: so that it turns into a log curve which looks
- 22:50Speaker 3: like you know, technology growth, but that's also how growth
- 22:52Speaker 3: works for people and their behavior and teams and their actions.
- 22:56Speaker 3: You know, it often starts looking pretty incremental, but over
- 22:59Speaker 3: time that reaches an inflection point. And so if you
- 23:04Speaker 3: believe in compounding, what that means is that you know,
- 23:07Speaker 3: in a given period of time, if you were to
- 23:10Speaker 3: only iterate once, let's say you you know, your version
- 23:15Speaker 3: was so good that it was twice as good as
- 23:16Speaker 3: the thing you did before, then now you have a
- 23:17Speaker 3: two x improvement. But if in that same period of
- 23:20Speaker 3: time you were to iterate let's say ten times, but
- 23:24Speaker 3: each of those times only make like ten to twenty
- 23:26Speaker 3: percent progress, you'd end up with a byproduct at the
- 23:29Speaker 3: end of that.
- 23:29Speaker 4: That's something like eight to ten x better.
- 23:31Speaker 3: So what matters, just based on kind of math, is
- 23:36Speaker 3: not like how good you are a version of a
- 23:37Speaker 3: version on something, but really the amount of times you
- 23:40Speaker 3: try and by trying me the amount of times you
- 23:42Speaker 3: put something out there and get feedback on it. And
- 23:43Speaker 3: I think that's true for basically every function. The amount
- 23:48Speaker 3: of times you show a prototype or a new feature
- 23:52Speaker 3: to customers and get their feedback. Often people you know
- 23:55Speaker 3: want to hold it and try and make it perfect,
- 23:57Speaker 3: but it's actually better to get it out there, get
- 24:00Speaker 3: because you're going to learn so much more about what's
- 24:02Speaker 3: good and what's bad, and be able to improve on
- 24:04Speaker 3: the good things and get rid of the bad things.
- 24:06Speaker 3: It's true in marketing where you're testing copy. It's true
- 24:09Speaker 3: in sales where the number of times you kind of
- 24:11Speaker 3: pitch something to potential customers. It's true in management where
- 24:15Speaker 3: you're asked feedback from the team. People don't like asking
- 24:18Speaker 3: for feedback because it's really uncomfortable to expose yourself and
- 24:22Speaker 3: to potentially be wrong and to hear things you don't
- 24:25Speaker 3: want to hear. But I think that's if you can
- 24:30Speaker 3: learn how to do that and be comfortable with the discomfort,
- 24:34Speaker 3: you end up gaining so much more and you end
- 24:36Speaker 3: up winning so much bigger because the end result is
- 24:40Speaker 3: so much better than anything you could have done in
- 24:42Speaker 3: the echo chamber of your own thoughts and beliefs.
- 24:46Speaker 1: Principle three says creating a calm, sustainable team culture with
- 24:51Speaker 1: no surprises and few fire drills leads to faster velocity
- 24:55Speaker 1: and better work. I feel like, in like all the
- 25:02Speaker 1: different organizations that I've worked with in terms of clients
- 25:06Speaker 1: of Inventium, and even within Inventium. You know, I can
- 25:10Speaker 1: think of so many surprises and things that come up
- 25:13Speaker 1: that you just could never have planned for, like that
- 25:17Speaker 1: are outside of our control, like a client requesting something
- 25:20Speaker 1: at the last minute, or a supplier changing the terms
- 25:24Speaker 1: of a contract or something like that. How again, how
- 25:28Speaker 1: does this actually work in practice at Almanac?
- 25:32Speaker 3: I think if I were to boil the modern work
- 25:35Speaker 3: method down to six words, it would be more structure
- 25:39Speaker 3: and more transparency if youwer meetings. And with this idea
- 25:42Speaker 3: that a lot of the work that humans I think
- 25:47Speaker 3: are meant to do should be creative work. But we
- 25:50Speaker 3: are spending a lot of time on repetitive processes that
- 25:56Speaker 3: aren't at all creative, and we are dedicating time. We
- 25:59Speaker 3: are tree reading things that happen continually as if they
- 26:03Speaker 3: are creative processes, as if they're new phenomena. When maybe
- 26:07Speaker 3: it's near the first time it happens, but if it
- 26:09Speaker 3: happens a second or third, or tenth or thirty at time,
- 26:12Speaker 3: it's something that we have seen.
- 26:13Speaker 4: It's something that we have done.
- 26:14Speaker 3: We may have been good at solving it or bad
- 26:17Speaker 3: at solving it, but we certainly have experience, and so
- 26:19Speaker 3: we can start to codify a process around it, learn
- 26:22Speaker 3: from what happened, and if we apply structure to it
- 26:26Speaker 3: and intentionality to it, we can take it from something
- 26:28Speaker 3: that takes creative brain power and turn it into something
- 26:31Speaker 3: that's more automated, something that we don't need to meet
- 26:33Speaker 3: about or talk about, but something that just runs smoothly
- 26:36Speaker 3: in the background of the organization. And so I think
- 26:40Speaker 3: a lot of what we are advocating for is even
- 26:43Speaker 3: things that might be surprises upfront.
- 26:45Speaker 4: Or things that might be unpredictable and when they start.
- 26:49Speaker 3: For at Almanac, it's things like customers filing tickets for
- 26:52Speaker 3: bugs or asking for future improvements, or the site going
- 26:55Speaker 3: down god for a bit.
- 26:56Speaker 4: You know, those aren't things we can predict.
- 26:57Speaker 3: But everything that happens after that moment is something that
- 27:01Speaker 3: we can handle. And even we can design a system
- 27:04Speaker 3: to account for the unpredictability and the risk there's that's
- 27:08Speaker 3: something humans do all the time with systems design.
- 27:11Speaker 4: Every system has.
- 27:11Speaker 3: A bit of ambiguity in it, and so there are
- 27:14Speaker 3: ways to mitigate or plan for that, uh, that uncertainty.
- 27:20Speaker 3: And the way the way you started just by recognizing
- 27:23Speaker 3: their's uncertainty and talking about and coming up with a
- 27:25Speaker 3: process as I'm sure you have a inventim on on
- 27:29Speaker 3: things like, you know, customer fire drills. I think where
- 27:32Speaker 3: a lot of teams go wrong is they don't something
- 27:35Speaker 3: happens the first time and it is truly a fire drill,
- 27:39Speaker 3: and then it happens the second time, and they treat
- 27:40Speaker 3: it as if the first time didn't happen, rather than
- 27:44Speaker 3: after it happens, doing a quick retrod and saying.
- 27:47Speaker 4: Hey, hey, what what just happened? How did it go?
- 27:51Speaker 1: Like?
- 27:51Speaker 4: Do we think it's going to happen again? And you know,
- 27:53Speaker 4: should we should? We build a process for it.
- 27:55Speaker 3: And I think the more structure you have and how
- 27:57Speaker 3: your team works, the more fire drills don't have to
- 28:01Speaker 3: be fire drills, and you can spend that time instead
- 28:04Speaker 3: on creative and meaningful work that is really moving the needle,
- 28:07Speaker 3: the reasons people actually wake up in the morning to
- 28:09Speaker 3: do their jobs and the reason the company exists, which
- 28:11Speaker 3: is to serve customers and add value.
- 28:15Speaker 1: I'm reflecting on the last couple of weeks at Inventium,
- 28:17Speaker 1: where I feel like we have had fire drills in
- 28:21Speaker 1: the form of consultants or inventeologists who were booked into
- 28:26Speaker 1: deliver workshops. One got COVID, another got really sick with
- 28:32Speaker 1: a flu like bug, and they were down and we
- 28:37Speaker 1: were like struggling to find replacements.
- 28:40Speaker 2: And I kind of I look back on that.
- 28:42Speaker 1: Now and it's like, that has happened many times in
- 28:45Speaker 1: the sixteen years that I've been running in Ventium. We've
- 28:48Speaker 1: never actually sat down and said, Okay, what is our
- 28:53Speaker 1: process for when this happens, despite the fact that it
- 28:56Speaker 1: has happened many many times in the time that I've
- 29:00Speaker 1: had this business. Sorry, it's yeah, for me, that's that's
- 29:04Speaker 1: really interesting hearing you, because I'm like, yeah, what about humans.
- 29:07Speaker 2: You can't pretty humans, But it's like, no, you can predict.
- 29:09Speaker 1: That humans will get seek and they will need some
- 29:13Speaker 1: sort of a replacement in the thing that they were
- 29:15Speaker 1: meant to be doing that week.
- 29:17Speaker 3: Yeah, you can certainly account for the uncertainty. There's whole
- 29:20Speaker 3: industries around this management.
- 29:22Speaker 4: That are about that.
- 29:23Speaker 3: You know, most of our legal and governance systems are
- 29:26Speaker 3: really about accounting for risk and uncertainty. And just two
- 29:30Speaker 3: antecdotes for you. One, when we started this work, I
- 29:33Speaker 3: used to think that people got satisfaction from work from
- 29:36Speaker 3: spending time on deep work. There's whole books that are
- 29:39Speaker 3: really great written about this, and I thought it was
- 29:41Speaker 3: all about flow and focus and that's where people find meaning.
- 29:45Speaker 3: And when I when we talked to these amazing professionals,
- 29:50Speaker 3: what people people evaluated whether a week was effective based
- 29:54Speaker 3: on if they got stuff done on their to do list.
- 29:56Speaker 3: And the enemy of getting stuff done is a fire drill,
- 30:01Speaker 3: and so what people hated them most wasn't that they
- 30:04Speaker 3: sometimes were just processing cast but it's when something got
- 30:06Speaker 3: in the way of them being able to.
- 30:08Speaker 4: Cross stuff off there to do list.
- 30:09Speaker 3: So it shifted our thinking from how do we enable
- 30:13Speaker 3: through our tool time for people to do deep creative
- 30:16Speaker 3: work to how do we help people just get through
- 30:18Speaker 3: their to do list faster so that they can get
- 30:21Speaker 3: done with their days get back to.
- 30:22Speaker 4: Other things that might matter them.
- 30:24Speaker 3: Because everybody hated ending a week feeling like they weren't
- 30:28Speaker 3: able to get important work done for with themselves and
- 30:32Speaker 3: their teams, and so this idea of minimizing fire drills
- 30:35Speaker 3: became an important principle to this end because it's not
- 30:37Speaker 3: just about something that makes the team move faster, but
- 30:40Speaker 3: it's also directly correlated to people feeling like their week
- 30:44Speaker 3: was a success and getting meaning and value from work.
- 30:47Speaker 3: The second idea to your point is that we love
- 30:50Speaker 3: the slogan from the US Marines. Slow means smooth and
- 30:54Speaker 3: smooth means fast. Where a lot of teams go wrong
- 30:58Speaker 3: isn't that they had to respond quickly to a new
- 31:01Speaker 3: event that they've never seen before. It's that they don't
- 31:05Speaker 3: stop afterwards, take a breath and say, like, what just happened,
- 31:10Speaker 3: how did it go? How do we make sure that
- 31:12Speaker 3: the next time this happens that we have some smoothness
- 31:16Speaker 3: in how we respond. Because this, when you have calmness
- 31:21Speaker 3: and order and structure, it's not just a more enjoyable experience,
- 31:26Speaker 3: it actually increases business and team velocity, and so you
- 31:29Speaker 3: can actually go faster while it feels like everybody is
- 31:34Speaker 3: moving at a sustainable pace. If you look at paddling races,
- 31:40Speaker 3: what you'll see is that the teams that win aren't
- 31:43Speaker 3: the teams with the strongest men. They're the teams that
- 31:46Speaker 3: are putting their paddles into the water at exactly the
- 31:48Speaker 3: same time. Because when everybody is moving together, you get
- 31:51Speaker 3: more momentum behind the boat, and that's much more important
- 31:54Speaker 3: than just like chaotic strength throwing stuff into the water
- 31:57Speaker 3: that actually ends up working at cross purposes. And so
- 32:00Speaker 3: what's critical is that a team is working together with
- 32:03Speaker 3: some structure, with some transparency, so that in the end
- 32:06Speaker 3: everybody feels like they're doing work that's sustainable for them,
- 32:11Speaker 3: but the whole boat is moving faster as a result, Adam.
- 32:15Speaker 1: For the listeners that want to connect with you, what
- 32:17Speaker 1: is the best way to do so and also to
- 32:21Speaker 1: connect with Almanac.
- 32:23Speaker 3: Yeah, So if you're interested in everything we've talked about today,
- 32:27Speaker 3: go to Modern work method dot com. I think we
- 32:30Speaker 3: have hundreds of free templates on there that help you
- 32:32Speaker 3: take a lot of these ideas and turn them into
- 32:35Speaker 3: practices your organization can use now. And if you're interested
- 32:38Speaker 3: in actually adopting a lot of these behaviors, the whole
- 32:41Speaker 3: point in building Almanac is to make it seamless for
- 32:44Speaker 3: your team just to start to work faster and better
- 32:46Speaker 3: without you having to spend time on it. And you
- 32:48Speaker 3: can get a demo and try out the product at
- 32:51Speaker 3: almanac dot io. And I think I'm on Twitter and
- 32:55Speaker 3: LinkedIn at Adam.
- 32:56Speaker 2: P Nathan Adam. I have loved this chat.
- 33:00Speaker 1: I feel like I've had quite a few penny drop moments.
- 33:04Speaker 1: That's really making me rethink how we do things at Inventium.
- 33:10Speaker 1: So I just want to say thank you for you
- 33:13Speaker 1: for putting such deep thought into how work can be
- 33:17Speaker 1: done better in this new world.
- 33:18Speaker 2: Of work that we're in.
- 33:20Speaker 1: I've personally just found our chat so incredibly valuable, So
- 33:24Speaker 1: thank you well.
- 33:25Speaker 4: Thank you very much. That's been funner.
- 33:28Speaker 1: I hope that you got as much as I did
- 33:30Speaker 1: from this chat with Adam. I know that it gave
- 33:32Speaker 1: me so many ideas to think about how we work
- 33:37Speaker 1: at Inventium, where we've been a remote first organization since
- 33:40Speaker 1: twenty twenty. And if you know someone who's currently in
- 33:45Speaker 1: the process of maybe rethinking how they approach their work,
- 33:49Speaker 1: maybe you might want to share this interview with them
- 33:52Speaker 1: to help spark some thinking. Thank you for sharing part
- 33:56Speaker 1: of your day with me by listening to How I Work.
- 34:00Speaker 1: Keen for more tips on how to work better? Connect
- 34:02Speaker 1: with me via LinkedIn or Instagram. I'm very easy to find.
- 34:07Speaker 1: Just search for Amantha Imba. How I Work was recorded
- 34:11Speaker 1: on the traditional land of the Warrenery people, part of
- 34:15Speaker 1: the cool and Nation. I am so grateful for being
- 34:19Speaker 1: able to work and live on this beautiful land, and
- 34:22Speaker 1: I want to pay my respects to Elder's past, present
- 34:25Speaker 1: and emerging. How I Work is produced by Inventium with
- 34:29Speaker 1: production support from Dead Set Studios. The producer for this
- 34:32Speaker 1: episode was Liam Riordan, and thank you to Martin Nimba
- 34:35Speaker 1: who did the audio mix and makes everything sound better
- 34:38Speaker 1: than it would have otherwise