Generative · loading…

Podcast: Creativity thrives on explicit contracts

Simone Cicero and I sat down to talk networked organizations and experiences from the field

There's a few moments in here where I realize that I am inventing a thing that has already been super well-documented elsewhere, but I think generally this is a pretty good podcast! I've been a fan of Simone for a long time. Do meet your heroes.

A few favorite bits.

Contracting for Creativity

You would think that when you focus more on internal pricing or you focus more on contracting with somebody, that you drain the impact out because all you’re thinking about is the price and the economics of the deal. But in fact, what I’ve observed personally in the work is that when organizations and when teams and when individuals focus on making that clear and clean—that economic contract between parties—and it might not be something that is explicitly paid. It might be a chargeback within an organization. Who knows? But as long as you make that clear, you start to have that growth of creativity that we’re describing before. Creativity thrives in structure. Okay. What’s the structure? Well, probably a contract. Okay. Well, how do we get more impact? We allow people to work more creatively. We give them more agency in their work. They create more impact. That comes back to better structure, better pricing, better economics, a better focus on the contract between parties.

How do you do this? A few ways that I wrote about in the book, like clear assets (maybe these assets are APIs or MCPs?) and standards (maybe a design system?), or clear CLOUs or Team Charters that declare relationships between units.

23. Domains, Assets & Standards
Clear ownership of domains and assets reduces friction; each team knows its decisions and resources.
40. Colleague Letter of Understanding
Explicitly document working agreements among colleagues.

Contracts redistribute power

Contracting and platforming of work is explicitly political, meaning it deals with how power is distributed, how it’s legitimized, how it’s contested, how it’s exercised. I think people are rightly observing that oftentimes the decisions that we’re making when we are explicitly contracting are not going to be good for them, or they’re not going to be good for people that they have kinship with. And that to me is a great signal. That to me shows me that we need to rethink the contract that we’re engaging in or the way that we’re developing a platform.

Coordination problems often conceal questions of authority...

Why Nothing Gets Done Around Here
Hundreds of thousands of hours are getting wasted on bad decision-rights. It’s got to stop. (Contains at least two good ways to fix this problem.)

But that's OK if you can harness it.

38. Conflict as a Resource
Treat constructive conflict as essential and beneficial for progress.

The more we give to computer, the more we want to give to each other

The joy that we get from our work is from, yes, achievement, but also from the people that we do it with. And I think that’s an interesting paradigm that we might see for these post-AI firms: that they are deeply focused on the human experience. And one cynical version of that is, “Oh, it’s like 996, and they’re just trying to make a buck, and they’re young, so they’re pushing each other to work harder and harder and harder.” But I think there’s something that is worth recognizing in this, and that is that, as we give more to the computer, we want to also give more to each other.

Which I wrote about in everybody's favorite essay:

The End of Role Clarity
Role clarity is a symptom of relational poverty, and small team with real trust are going to out-deliver our absorptive capacity unless we do...something.

Simone's writeup on the ep is here, on his new Boundaryless site. It's nice.

Clay Parker Jones on Why Agency Needs More Structure
Clay Parker Jones and Simone Cicero explore how clear contracts and explicit rules of the road give people more room to act and to create.

Transcript

Simone Cicero (00:45) Hello everybody, and welcome back to the Boundaryless Conversations Podcast, where we explore the future of business models, organizations, markets and society in our rapidly changing world. I'm joined today by Clay Parker Jones. Good to see you.

Clay Parker Jones (01:02) Good to see you too. Happy to be here.

Simone Cicero (01:04) Thank you so much. Clay leads Organizational Design and Development at Airbnb, where he works on how structure, decision-making and other aspects of organizational development coalesce in a fascinating, I would say unique, platform environment. Before that, he co-founded August, an employee-owned organizational design consultancy. He has more than 15 years of experience developing a body of work, and plenty of writing, around one key question: how do we create organizations that give people room to act without losing coherence? That is also a crucial question in our work at Boundaryless.

Clay also has a book out, published in March: Hidden Patterns: A Playbook for More Human Workplaces. It's one of those books you want to buy in paper, because you want to take notes and bring it with you into the field. So again, thank you so much for joining us.

Clay, as an opening question: your work seems to have moved from a strong belief in self-organization towards the recognition that agency needs more structure to really work well. My own work has probably moved a little in the other direction. So maybe we can start there, and you can confirm or challenge that statement.

Clay Parker Jones (02:51) I think that's a good read. Generally speaking, I, and maybe others in the movement, if we can call it that, have been a little too optimistic about self-organization, especially in large, complex organizations where the dominant mode of organizing is something else: more directive, more top-down.

It's something I've experienced and spent a lot of time building for my own organizations and teams, but it always comes up against reality: we live in an organizational and social context that sometimes prevents us from realizing the gains that self-organization might bring. My journey from August to R/GA and Black Glass, working in a more traditional consulting environment, without expressly trying to bring self-organization to teams and organizations, and then to Airbnb, has been a journey toward understanding how important structure is: both its explicit versions and its tacit, hidden versions. And what we might need to do about those parts of the organization that live alongside the self-organized, emergent way a firm, a team or an individual develops.

One of my major mistakes was believing that self-organizing was morally cleaner or better than top-down organizing or structurally driven organization design. That's a flawed choice. Both are important. Both are real. And as designers, as people who shape systems like these for commercial good, human good, stakeholder good, we have to be alive to both sides.

That has been my journey, and I'm still on it, trying to understand how the two traditions come together, how they can live alongside each other, and how we can help more people experience the benefits of both. I don't have an answer yet, but I'm eager to keep discovering it alongside teams.

Simone Cicero (05:42) While you were speaking, I was picturing this on a piece of paper. You're using "structured" versus "self-organized" as polarities, but maybe the polarities are top-down governed, managed, versus self-managed, and structure sits in the middle as an enabler of some kind of delegation process. Does that resonate?

Clay Parker Jones (06:19) Yes. One way to think about what you're describing is that it's fractal. In every team, a self-organizing process will have an inherently top-down aspect. There is usually some sort of team leader, and they are typically selected by an outside body rather than elected. That leader needs to confer authority on the self-organized work, so that act is itself a bit top-down. And at the broader level, all organizations are self-organizing.

It's useful to describe these as polarities, in opposition, because that helps us understand what we're dealing with, but it isn't how it happens in practice. There are some things we do to make sense of things in our human brains, and other things we do to actually bring them to life. We need to recognize authority at the team level, and we need to recognize self-organizing at the broader organizational level. An organization of 7,000 people will inherently be self-organizing to some extent, using the structures, guidelines, rules, norms and culture that allow them to do certain things and not others. It gets philosophical quickly, but I do think both of these live at all times in every single organization.

Some writers focus more on the self-organizing side, and others on the structured, governed, top-down side. Bringing them together is something most leaders rarely get to practice, because the top-down, governed side of the picture is the one that gets most of the leadership group's attention. When we're at the top of an organization, that's how we see the world: as something to wield and implement for stakeholder or shareholder gains, depending on our view. So yes, I love that provocation, because we do have to think about both at all times.

Simone Cicero (09:00) There's another element that comes into this picture for me. On one side, you have organizations where the brand plays a larger role and the organization is closely identified with its product, sometimes a single product, or a single experience, like Airbnb. On the other side of the spectrum, you have companies whose brand is perceived more as an incubator of multiple brands and companies. Let's skip the typical Haier example and take Flagship Pioneering instead.

In both types of organization, you always have the task of empowering people to do more, simply because you don't want to micromanage everyone. But in the brand-sensitive company there is a much more recognizable creative leadership, a creative hierarchy, which I believe is a topic we don't talk about enough. In that case you have one type of governance process; in the other, a governance process more oriented to investing, and so on. Yet in both cases, making the rules of the game explicit, how the organization works, which decisions are pushed to the edge, how people take on responsibility and accountability, is important. So, in your experience, how do you tweak the system so that people are empowered to actually do the work, while still respecting the rules the organization has defined for them?

Clay Parker Jones (11:50) Great question. There are at least two concepts in what you described, and they may be impossible to fully separate. One is the essential nature of the firm: is it a portfolio of brands or a single brand? Does that determine how the organization operates, and does it animate a particular form of organizational design and governance? The other, related but quite different, is how great creative works come to life. A creative work could be a movie, a brand, a product, an app, or an organization, over a long period of time.

Digging into both is critical, and you're right that the second is the one we spend less rigorous time thinking about, because it seems "other": we assume we can't really understand or write down the creative part, and that it can't benefit from governance, which is far from true.

On the first question, take an organization that isn't known for being self-organized and that we never talk about in the movement's literature: PepsiCo. A global company with massive economic impact, hundreds of brands, if I'm not mistaken, operating in hundreds of countries and trying to manage the coherence of brands, products, and delivery systems. You can have plenty of critiques of them, and good ones, about plastic use, sugar consumption, and so on. Setting those aside to look at how they're organized: they spend a huge amount of time thinking about the operating system that holds the whole thing together and makes it work across time zones, geographies and cultural norms.

You would assume a company that size is fairly strictly top-down. But having consulted with PepsiCo for many years, across a couple of companies, I've seen that they really do try to figure out this empowerment question. They do it for the growth of the businesses they own, and also for the development of their people, their human capital. They spend an unusually large amount of time working out how to invest authority in leaders who may eventually become the CEO of a business, the president of a region, or a senior functional leader. You wouldn't look at them and say "that's a networked organization", but in fact it is, precisely because they invest so much time in thinking about how the network operates.

Much of that comes down to the brand: figuring out what the Pepsi trademark, Pepsi Max, or Cheetos are meant to mean to people around the world, and keeping those meanings true both at the center and at the edge. Every self-organized, more democratic, more emergent or more responsive organization can look up to this: the intensive focus on people development, on investing authority, and on making the rules of the road clear enough that the system can operate independently and autonomously across thousands of individual consumer touchpoints. Generally speaking, portfolio organizations have done a really good job of this, and we can learn from them about combining top-down and bottom-up ways of engaging with the business. That's the first part, do you want to jump in?

Simone Cicero (17:00) No, please, take the space.

Clay Parker Jones (17:12) Then there's the creative side: how do great creative works come to life? Rick Rubin's recent book, which was very popular, helps people understand exactly this and how they can be more creative in their work. I really like it. He's known for a relatively hands-off approach; there's that famous interview where he says he has no special musical talent; he just knows what he likes when he hears it, and he creates the environment in which artists can do their best work. People are now relating that to vibe coding and all of that.

At the same time, look at Pixar, or, again, PepsiCo, which does a pretty good job of managing the creative process across hundreds of thousands of employees. Pixar is famous for the structure it puts around the creative process and around how feedback is given. The Pixar Braintrust is a meeting format where participants have no authority over the product or the outcome, yet they're asked to give deep, constructive feedback. There are rules and guidelines for how the Braintrust works and how people on both sides, feedback givers and receivers, are encouraged to participate. What we're noticing now is that the creative process benefits deeply from rules.

We've always said creativity loves structure, but we've been hesitant to apply the amount of structure needed to let creativity emerge in organizations. My personal view is that those structures, safety nets, boundaries or guidelines for how people deliver, whether that's a design system or simply a purpose statement that gives a lot of clarity about what we should and shouldn't do, are where creativity comes from.

I remember talking to a mentor of mine, Debra France, who led leadership development at W. L. Gore for a number of years. She told me that at Gore they paid a lot of attention to the things that were hard and the things that were soft. They understood they needed both, hard rules and soft rules, hard skills and soft skills, that these are different, and they were fine with letting them be different. I think that's critical: organizations that get a lot of creativity from their people, whether networked or monolithic, spend a lot of time being clear about the rules of the road and making sure everybody understands them.

The rule of the road might be that the top person in the organization makes all the decisions about the product. We're better off if we're very clear that this is the case. Or it might be that we have to follow the guidelines put in place by the design team. So there are two things happening: a deep structural capability that many large organizations are very good at, and that we can learn from; and the recognition that creativity benefits from structure. When we're clear about the rules, we get more from our people, especially when some of those rules give them the safety to try things that the people who set the rules may never have imagined.

Simone Cicero (21:27) I have two pages of questions, so let me try to synthesize.

My first reflection is that a lot of the work we've done in organizational development, and you mentioned PepsiCo, is about making a product consumable in as broad a set of places and contexts in the world as possible. It's about growth and scale. We want to make something scale, standardize certain practices, and at the same time keep people engaged, expressing their creativity, and enabled. But in the end, we still largely treat people as "instructables".

On the other hand, companies like Airbnb, or others with a clear footprint in the real world, don't just have employees: they have constituents. For Airbnb, that means guests and hosts, some of whom make a living through the platform. And, as we've seen a lot with Airbnb, these guests and hosts live in living systems: they have impacts, they live in cities, and so on.

So my question is this. We now have a stronger systems-thinking capability, and AI models help us: as long as we have a good way to describe the organization, the products, the constituents, and the context, they give us a much broader understanding and analytical capacity. Do you see organizations becoming more keen to think about their business as situated in the multiple contexts where it exists? Is this a conversation you're seeing in the field, always in service of a healthier business and a healthier vision of what a company should evolve into in the world we live in?

Clay Parker Jones (25:21) The useful thing to pick up there, for me, is again a polarity: instructables versus actors with agency. Are the people we employ directly under our active control, and to what extent? And then there are more networked organizations, organizations that benefit from any kind of network.

Generally speaking, organizations, whether they see themselves as networks or not, benefit from thinking of themselves as networks. Haier is probably a good example. Even PepsiCo has a distribution network and a bottling network that it doesn't fully own. All organizations, I would argue, benefit from seeing themselves as a network, whether that's their internal employee network or an external network of constituents, and from creating a more porous boundary between the paid, W-2 version of the organization and the rest, contracted labor, partner labor, the partner workers of the organization.

Simone Cicero (27:52) Yes, "partner" works quite well.

Clay Parker Jones (28:14) It's good to think of it that way. And if you think of your employees as partners, really, not in some empty values statement, you'll get more out of those people. Consulting organizations get a lot out of people both while they're paid by the organization and after they leave and pay the organization back through client fees, because they see those people deeply as partners, not just over an employment contract but over the lifespan of both the company and the person: people who go on to do the organization's work even beyond the employment contract. That's something we can all get better at.

It doesn't have to be an organization like Airbnb with guests and hosts. We can all see ourselves as part of a constituent network. I think that's what stakeholder capitalism was trying to do, and maybe didn't quite achieve as well as we wanted, and there's work to be done within organizations to bring it to life. To me, these things are fully compatible: they're points on a spectrum of truly caring about the impact that employees or partners can have on the economics of the firm.

When you start setting up structures that enable more of that, with more benefit on both sides of the equation, we all do a lot better. Those organizations live longer and persist through hard times. That's what we're after, because more people are built into the design and the longevity of the idea, the creative idea.

Simone Cicero (30:02) I think I got quite an interesting insight while you were speaking, and since it doesn't happen often on the podcast, it's worth celebrating. Take stakeholder capitalism: there's a company, the company wants to do good, so the approach is somewhat patronizing: "as a company, I can positively impact the world". I've always been very skeptical of these impact theses, even setting aside ESG, CSR and the like. That's not to say no company has ever had a positive impact; some have.

But what I'm perceiving is that we're at the dawn of a moment of making things explicit. AI is coming into the world and telling us we have to make things explicit and legible. There's pressure to make systems visible, our companies, our customers. Jack Dorsey has been talking about company world models, customer world models: modeling the universe a company operates in. For me, there's a potential there. If an ecosystem manages to make explicit the relationships among all its players, along with the impacts and the constraints, then maybe we stop thinking about the organization as a driver of impact.

Instead, the organization has an opportunity to help the whole ecosystem of partners, stakeholders and constituents see the problems and opportunities they're involved in. And maybe we can move towards a kind of self-organizing where all players in the ecosystem recognize that they have agency, responsibility and accountability for the problems and opportunities around them. It's no longer just the company doing positive impact, but the company participating in a system: I'm a partner, I can partner with you, we can have a shared contract to make a product; there's a stakeholder; we have resources we pool; maybe a common language we maintain together.

So it's a shift from companies impacting the world to ecosystems becoming explicit and legible. Companies can, first, facilitate this process, that in itself is a good way to have an impact, and then participate, along with other partners, in a value-creation process where everybody can see their role, their contribution, the resources they rely on and the contracts they sign. That's what I was thinking in the background as you spoke.

Clay Parker Jones (33:44) That's great. It reminds me of one of my favorite quotes about platforms, and also of a lot of your work on pricing in organizations, which I think is spot on and something we all need to get better at. The quote is from Bill Gates, and it circulated when organizations were talking about platforms more frequently, maybe eight or nine years ago, as something they wanted to become good at.

Simone Cicero (34:23) Yes, I made a living out of that for a decade.

Clay Parker Jones (34:44) Right. And one of the cool things right now, observing how AI is affecting organizations and working culture, is how many organizations are focused on platforms again, and how excited we all get when a new platform or a new infrastructure technology comes to life. Nobody cared about infrastructure technologies two years ago, and now it's all we can talk about, everyone is excited about ultra-cheap models and the new infrastructure around them. It's amazing that we've reached that point culturally, because infrastructure is what matters.

Anyway, the Bill Gates quote I love is: a platform is when the economic value of everybody that uses it exceeds the value of the company that creates it. A platform is something that happens, rather than something that is. And to me, the interesting paradox in our work, it would need to be tested, is that you get more positive social impact when you focus more on the contract. You'd think that focusing on internal pricing or on contracting drains the impact out, because all you think about is price and the economics of the deal. But what I've personally observed is that when organizations, teams and individuals make that economic contract between parties clear and clean, and it might not be explicitly paid; it might be a chargeback within an organization, you start to see the growth of creativity we described earlier.

Creativity thrives in structure. What's the structure? Probably a contract. How do we get more impact? We let people work more creatively and give them more agency in their work, and they create more impact. That comes back to better structure, better pricing, better economics, a better focus on the contract between parties. I find that a really interesting paradox that I haven't seen expressed much in the work yet. Maybe it's just a version of "creativity loves structure" and I'm high on my own supply here.

Simone Cicero (36:55) For me it resonates strongly with the idea of enabling constraints.

Clay Parker Jones (37:01) Yes, it's the same thing. It's not a new idea.

Simone Cicero (37:23) I wasn't criticizing you for not being new, it was interesting to hear, because we're used to platforms. And what do platforms have? A clear product interface, which is a contract. An open-source license is a contract. A product you can consume is a contract. We're not used to contracts, especially inside organizations, because we're used to bureaucracy and informality, to what Chase Chapman calls "socialware". For many years we've assumed we don't need explicit contracts inside organizations. Yet the most successful company in the world, Amazon, has had internal contracts for more than twenty years.

The interesting segue, and we spoke about this, is that writing an interface, a contract, is a political act, because it's constitutive: you create a shared understanding, a shared interface. Especially inside organizations and ecosystems. Take an open standard: I'm working with clients who have run a business for 50 years, and suddenly policymakers are telling them that at a certain interface there must be an open standard. The whole world gets restructured around that, because profits migrate and things shift underneath. When a policymaker does it, we recognize it as political. So whenever you set a contract, even inside an organization, it's a political act: it redistributes power in certain ways.

So maybe the straight question is: are we concerned about this because, inside organizations, people aren't used to managing the political implications of what happens?

Clay Parker Jones (39:44) I agree 100% that contracting and platforming work is explicitly political: it deals with how power is distributed, legitimized, contested and exercised. What's worth digging into is whether people dislike it, whether we see it as bureaucratic and want to reduce formality or the appearance of power in our day-to-day work, or whether we lack the maturity of language or response to deal with it. Or, in most cases I've observed, whether we are repelled by facing the outcomes of the political decisions we're making: who we're empowering, who we're disempowering, and whether that's economically beneficial for me as an employee, or for people like me inside or outside the organization.

I think it's mostly the latter. People rightly observe that the decisions we make when we contract explicitly often won't be good for them, or for people they have kinship with. And to me that's a great signal that we need to rethink the contract we're engaging in, or the way we're developing a platform.

I mentioned this on another podcast recently: one of the rules we had at August for a while was, don't try to convince people that self-organization is good. Let them find their way to it, if they're going to. But we do need to hear why they don't want to do it, why they don't want to come along with us or with the emerging majority, because they probably have a really good signal. Maybe middle managers are losing authority as we move to a more contract-based way of working, because the contract is doing what the managers used to do. We should pay close attention to those objections, even if we're not trying to convince those people to come along.

So I think it's the latter, and it's something we all need to get better at in terms of skill rather than maturity. They're not instructables; they're people with agency and goals, and they can do amazing things. Even people previously seen as low performers can become high performers in the right context, maybe in another organization, but certainly also somewhere within their current employment.

In any case, we need to lean into building the skill of contracting, especially now, as we see what AI needs to do its best work. It needs a constitution, rules of the road, things it's not allowed to do. If we're lazy about those things, or deliberately a bit curious about what a computer, or people, might do with a lighter boundary around what's allowed, we'll get the outcomes we deserve. Thinking more about contracting, structure and the governance of the organization, both human and machine, is going to become one of the most valuable skills today. Organization designers may have it in spades, but we need to train people in it, because most managers aren't good at it yet.

Simone Cicero (44:54) I was thinking about the value of making things explicit, contractually or more generally, the value of making a language explicit. When we say "contracting", it's a metaphor for making the rules explicit. I come back to Jeff Bezos's API mandate: an API is a contract.

Clay Parker Jones (45:19) I love that.

Simone Cicero (45:37) So what are the benefits of making things explicit versus not? Making things explicit means you surface a lot of the debt that hides in an organization behind what isn't explicit, organizational and technical debt. So generally speaking, it's good for the organization. And I'm not saying it's bad for employees, nor assuming employees want to protect that debt; the debt is the result of much deeper problems in organizations. Overall, it's good to make things explicit.

So why don't certain companies do it? I believe it's because their boards and executives are willing to take on more risk, since anything that isn't explicit can hide a lot of debt and problems. They're willing to take more responsibility for continuously reading, understanding and steering the organization in a certain direction. Even if that means treating employees more like instructables, they believe they can shape the organization and motivate people in other ways, with a brand story, for example. Those are the two polarities I see.

The other question I have concerns AI, which is clearly pushing for explicitness, we've seen it. For me, it's an opportunity, because our task in organizations today, quoting my friend Indy Johar, is to understand what it means to be human in organizations now. The risk is that if we just push humans to the higher level, abstractions, design, constraints, we're only moving the ball up, and AI will catch up. The only way to make humans truly valuable is to give them the possibility to engage with the context. When we create these contracts, APIs and interfaces, we enable people to define performance, another point you raised.

If everything becomes explicit, performance can be defined very differently depending on where in the organization you attach your initiative: a partnership, an investment, a new product where you take risks. There isn't one single model of performance everywhere. If you're more entrepreneurial, performance may mean taking more risk; if you're more executive, it may mean improving EBITDA or saving money, and you can get some skin in the game that way. These are just a few ideas, but I think you're right that this is the new playbook for HR, and an open playbook for organizational design. It's very important for companies.

Clay Parker Jones (49:01) A few things there. Why do organizations resist making their operating model, their way of working, explicit? I see three reasons.

The first, which I've observed directly talking to leaders in fast-growing AI-native firms, is speed. "We don't have time to write things down. We're a year old, or a few months old. And AI will help us manage the context and make things explicit anyway." Do we need to write down our roadmap when it changes every five minutes? Maybe, maybe not. Do we need to write down who makes which decisions? Again, maybe not, because we can just ask the all-knowing central model, which, honestly, is just a Markdown file in GitHub that can tell us how we've made decisions over time. That certainly makes sense.

The second, especially in organizations that have gone through a phase transition from pre-AI to post-AI, truly delivering value and operating with AI deeply and natively in their work, is that some people still remember that information is power. Having information made explicit and placed somewhere accessible takes some power away from them: they know how to get things done, and helping others know how to get things done doesn't benefit them. It may not be a conscious choice, but we've observed that some people resist making the guidelines explicit.

The third, which I don't quite know what to make of, shows up in two ways. One is the belief that managerialism is lame and inherently bureaucratic. The other is the belief that if we invest a lot of labor in making our business more bureaucratic, we'll sap our people's creativity, because they'll think more about the rules of the road than about the human next to them and how to get creative work done.

So: speed, power, and an anti-managerialist flavor that can be either anti-bureaucratic or pro-human. I think all of these are false choices, or bad compromises. The fast organization can certainly spend a bit more time, or ask an agent, to work on its organization design and make explicit what needs to be explicit. Start now, not later. On power: you'll gain more power by making things explicit; I don't believe hoarding information is the right path forward, although people definitely do it. And the idea that managerialism will sap our creativity is simply wrong. We've seen it in every case, whether it's a piece of creative art that needs structures around it to come to life, or Amazon with its many years of contracting.

Simone Cicero (55:44) Let's move towards a close. I'd like to ask you to wrap up your ideas from today's conversation and connect them with what you see moving forward, in your work and in the practice more broadly. Then I'll ask you for the breadcrumbs: a few readings, podcasts or other things you want people to check out.

We discussed a lot, and I found it an incredibly generative conversation, I have several pages of notes to go through. You've also done retrospective work for the book, which is a culmination of many years of practice, so you have a clear idea of what it means to build organizations in a certain way. Imagine this conversation sits between that past experience and the future you can see. What do you see moving forward? And if the future is hard to anticipate because it's such a moving target, what excites you about your work at Airbnb, or about the practice of organizational design and development in general?

Clay Parker Jones (57:20) One of the critical things I've learned is that organization design, in its explicit, practiced forms, needs to be democratized and made doable, at a high level, by more people. Right now, I observe that organization design is being done largely at a prosumer level. It's usually not done by trained consultants but by middle and senior managers making decisions based on the inputs they've been getting for a long time: the rising and falling stars on their team, who deserves more power in the system. It's very human and very personal, and usually not especially structural. Not always, but most of the time. What we need to do as a profession is make it easier for more people to come into contact with this work, and to see organization design as a valuable practice that managers engage in frequently.

What I personally would like is to work toward a future without organization designers. When we think about the normative space we're trying to enter, this is a profession that should be "eaten" by other people doing the work themselves. It's about handing the keys over to executives and to people, top-down and bottom-up, so they can make their organizations better.

That relates to a point you made earlier that we didn't fully get to: what are humans for in organizations? They're for each other. The joy we get from work comes from achievement, yes, but also from the people we do it with.

I think that's an interesting paradigm we might see in post-AI firms: a deep focus on the human experience. The cynical reading is that it's "996" culture, young people pushing each other to work harder and harder to make a buck. But there's something worth recognizing in it: as we give more to the computer, we also want to give more to each other. I want to build a future where more people give more to each other and are more creative with each other rather than against each other. And I think that happens by giving more people the keys to the kingdom, so to speak, to dig into organization design together, at the team level and at the leadership level.

Simone Cicero (01:02:08) I agree, and if I can add a perspective: this needs to come with a first-person dimension. People need to engage in organizational design, not for its own sake, but because they are accountable for what they design. That's how I'd complement your point.

As we close, is there anything you'd like to suggest to our listeners? We typically do a couple of breadcrumbs: something you've been reading or listening to that they shouldn't miss.

Clay Parker Jones (01:03:18) A couple of things. First, a book by Bree Groff, a fellow organization designer and thinker, working a little to the side of my work. She was CEO of NOBL for a while and then at SYPartners, and she wrote Today Was Fun. It's exactly what it says on the tin: getting more fun and joy from our work, and recognizing that this doesn't conflict with getting big, important creative things done. I love that book.

Another one I've just picked up, I have it right next to me, is The City as a System.

Simone Cicero (01:04:04) Yes, this will be a video podcast.

Clay Parker Jones (01:04:08) Beautiful. It's exactly the kind of book I love to page through and read bits of, and it deals with many of the organization design topics we think about, expressed in the form of the city. It's published by Trancity Valiz. Just a very cool object; I really love it.

Another person I'd point to is Melissa Valentine, her book Flash Teams, and her work in general. She's doing tremendous work at Stanford, including at Stanford HAI. A really phenomenal thinker and a generous soul; I've had the pleasure of speaking with her in depth over the last several months, and I'd point people to whatever she's working on.

And podcast-wise, what I've been listening to regularly is In Our Time, from the BBC. I just love it. It's a deep dive into topics both straightforward, like the origin of trees, and philosophical, like the idea of liberty. A wonderful history podcast, and it's what I listen to when I'm feeding my son at 4 a.m.

Simone Cicero (01:05:39) Thank you so much. It's a bit unusual for guests to suggest things that aren't strictly work-related, so it's good to have such an unusual breadcrumb. I know you have a newborn at home, so thank you for making the time to join us. I think it was a tremendous start to the season, and I hope you enjoyed it too.

Clay Parker Jones (01:06:11) I did, I really loved it. Thanks for having me. It's great to finally chat live with someone I've looked up to for such a long time. I love your work and I hope we do more of it together in the future. Even if organization designers aren't part of the future I envision, thinking about the future of the work is critical.

Simone Cicero (01:06:33) Thank you so much. And for our listeners, head to boundaryless.io/podcast, where you'll find the show notes and all the links we discussed today. Until we speak again, remember to think Boundaryless.