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