
Agile Digital Transformation · 2024-12-27 · 33 min
Key moments - from our scoring
Substance score
37 / 100
Five dimensions, 20 points each
Andrew Davis explores why traditional leadership approaches fail in modern distributed organizations where digital technology has created speed, scale, and information overload. He identifies three core organizational afflictions - disengagement, disorientation, and distraction - that emerge from remote work, time zone distribution, and information velocity. Davis then introduces transformational leadership through the VAST framework: leaders must articulate Vision, model Authenticity (undergoing personal transformation themselves), provide Support through genuine investment in team members' development, and Transmit full authority and responsibility to enable autonomy. A critical insight for technical leaders: the debugging mindset that made them successful engineers - where problems have observable solutions and stay fixed - doesn't apply to people. Trust cannot be consciously enabled; it emerges through slow, deliberate investment in understanding others. Davis notes that technical professionals often chose computers over people early in their careers, creating a deficit in psychology, sociology, and communication skills that become essential later. For IT and engineering leaders specifically, transformational leadership becomes both more necessary and more foreign, requiring them to backtrack and develop the soft skills their technical trajectory allowed them to avoid.
Disengagement (difficulty feeling emotionally connected to colleagues and the organization's mission), disorientation (being overwhelmed by information velocity and not seeing the big picture), and distraction (an explosion of meetings and parallel projects pulling focus in different directions).
Vision (articulating direction others don't yet see), Authenticity (undergoing personal transformation yourself rather than just directing others), Support (investing time and resources to understand and develop each team member), and Transmission (delegating full authority and responsibility so people have autonomy).
Technical professionals typically chose to work with computers over people early in their careers, creating skill gaps in psychology, sociology, and communication that become critical when they move into leadership roles managing people.
IT professionals are rewired to expect problems to solve in milliseconds to hours, so they underestimate the slow, deliberate time required to build trust, break down complex work, and develop team members through mentoring.
Trust is visceral and builds through consistent presence and investment; in distributed teams without physical proximity, leaders must be intentional about understanding each person's unique needs and demonstrating authentic care through their actions.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode surfaces a few interesting frameworks (VAST acronym, three organizational afflictions from Flow Engineering, Buddhist six practices applied to business) but spends too much time on high-level platitudes and meandering analogies. Actionable insight per minute is low, with large stretches of obvious observation.
the three main afflictions we experience are disengagement...disorientation...and distraction
from giving comes wealth. That's a little bit paradoxical
The Buddhist monk background applied to technical leadership and the video game avatar metaphor for leadership development are genuinely unusual angles for a B2B podcast, but much of the surrounding discussion (remote work trust, distributed teams, psychological safety) is well-worn territory and the VAST acronym repackages existing leadership theory.
my background prior to becoming, going full time into it. I'd spent 15 years as a Buddhist monk
we've got to debug the stack on which our conscious experience is operating
Andrew Davis is a CPO and published co-author with a genuinely unusual background (15 years as a Buddhist monk before entering tech), which gives him an interesting practitioner lens, but the conversation reveals little evidence of having led transformation at significant scale and he operates more as a thought-leader/author than a scaled operator.
I'm the Chief Product Officer at Autorabbit and author of Flow Engineering From Value Stream Mapping to Effective Action
it's a work in progress and, and a lot of my interest in this area comes from my own challenge to figure out how can I be, you know, the most effective technical, technical leader
The episode is almost entirely abstract - no named company examples, no metrics, no timelines, no dollar figures. References to existing books (Flow Engineering, Leadership is Language) are the only concrete anchors, and even those are mentioned only in passing without substantive detail drawn from them.
in the book Leadership is Language by David, uh, Marquet, he also talks about this Leader leader model
we talk about three main afflictions that arise as a result of scale
The host makes some reasonable connective observations and asks a mildly probing question about whether transformational leadership fits IT teams, but defaults repeatedly to praise and summary rather than genuine follow-up or challenge. No claims are pushed back on and several interesting threads (the Buddhist practices, the delegation issue) are left undeveloped.
that was a very, very, very good point right there at the end
I was thinking this conversation was actually suspiciously spiritual. I love it
Computed from the transcript - who did the talking, and the words that came up most.
Andrew Davis is the Chief Product Officer at AutoRABIT and the co-author of Flow Engineering: From Value Stream Mapping to Effective Action . Andrew co-authored the book together with Steve Pereira, with whom they also host a podcast and whom we've previously had as a guest on our show and discussed flow engineering. In this episode with Andrew, we talk about the concept of transformational leadership, with him sharing his approach to training technical leaders. Links & mentions: agiledrop.com/podcast/steve-pereira-flow-engineering linkedin.com/in/andrewdavis autorabit.com amazon.com/Value-Stream-Clarity-Steve-Pereira youtube.com/@flow-engineering
Transcribed and scored by The B2B Podcast Index.
Speaker A: That whole learning journey of really understanding what's this, what's, to use a technology term, what's the stack on which our conscious existence is operating? And we've got to debug the stack on which our conscious experience is operating. We want to really be maximally effective, individually or collectively.
Speaker B: Welcome to the Agile Digital Transformation Podcast, where we explore different aspects of digital transformation and digital experience with your host, Tim Butera, Content and Communication Manager at ah, Agile Drop.
Speaker C: Hello everyone. Thanks for tuning in. I'm joined today by Andrew Davis. He's the Chief Product Officer at Autorabbit and author of Flow Engineering From Value Stream Mapping to Effective Action. This is a book that he co authored with Steve Pereira and we've actually previously had Steve as a guest on our show. Uh, we talked about flow engineering and we'll make sure to link to that episode in the show notes of this one for anyone interested. And yeah, today Andrew and I will be actually tackling the topic of transformational leadership. I'm sure it'll be a good one. Andrew, welcome to the podcast. Thank you for joining us. Really great to have you here. Uh, want to add anything before we dive into the questions?
Speaker A: No, I'm really delighted to have a chance to be here, Tim. Thank you so much for the invitation and uh, delighted to meet the Agile Drop and digital and Agile Transformation crew.
Speaker C: Thanks so much for joining us, Andrew. As I said, I'm also happy that we got in touch and that we agreed to speak and about really important and interesting topic, as I said, transformational leadership. But before we define this and talk more specifically about transformation leadership, I want to set the stage by us, uh, discussing the main challenges or maybe the main obstacles that leaders face in the current digital economy.
Speaker A: Yeah, uh, it's a vast question. It's a good question. I'm not sure I could give a definitive answer to what the main challenge leaders face. And obviously it's very circumstantial, but depending on the leader and the situation. But the things that are top of mind for me in terms of general challenges for leaders are first of all, a time of such incredible rate of change, pace of change, the fastest pace of change in the history of our species. Um, one of the fastest paces of change in the history of the earth and we are struggling to adapt, I would say, um, we have a lot of preconceptions about what it means to be a leader. Preconceptions about what companies are like, preconceptions about what, what it means, you know, what, how employees should act these kinds of things. And these are not necessarily keeping up with the full pace of change and the full scale and scope of what we're dealing with today. So one thing that's on my mind a lot is with what it has enabled is this incredible globalization of organizations where information flow is so much faster and cheaper and easier than it ever has been before. So you can create and you can sustain global digital enterprises. You can have companies where everybody is distributed around the world. You know, video conferencing has been popular in some crews for, you know, 20, 25 years, but it's now ubiquitous. It's, it's, you know, this, uh, you have, so you have people who are distributed across the world and by virtue of being distributed across the world, they're also distributed across time typically. So you've uh, got people in different time zones and so forth. So you're not coordinating in physical space as much these days. And we evolved to coordinate in physical space. And so there's a lot of sense of orientation that we derive just by being in the same physical space together we get a feeling for people on an emotional level in addition to just knowing the explicit context of what's being discussed. And that is really important for building trust and connection with others and a shared sense of common purpose. And in the absence of that in person interaction, it can be, I think, quite difficult for people to feel fully connected to their co workers. A deep sense of trust, alignment, connection. Because you're not in the same physical space, you're you and you also don't have access to the same information. There's such a fast pace of information flow that uh, it's, it's possible for you to spend your entire day just trying to keep up with information in your domain. And you're getting information that may be totally different from the information many of your co workers are. And so there's this. The amount of information and folks being distributed across time and space creates, I think, a great disorientation where different people may be each on their own laptops, looking at their own kind of world, not necessarily very oriented to the whole of what the company is trying to do. And so in the book Flow Engineering, we talk about three main afflictions that arise as a result of scale. But we need to understand that the scale of modern organizations is created by IT technology to a great degree. I mean the speed and scale would not be possible, um, without digital technology. And the three main afflictions we experience are disengagement, which is that it's hard for us to really feel emotionally connected with each other or emotionally connected with the customers and the main mission of the organization, that it's very easy to split off and get a little bit focused just on your own particular needs or your own department's needs and not really see the big picture. Disengagement is one, disorientation is the other. I think because of the, just the massive amount of information that we're presented with, difficult make sense of all that information and then distraction. And when you have people who are disconnected from each other, they're working on separate projects and so they each like need to get their projects done. So they ping other people around the organization to get that work done. And you get this explosion of meetings and simultaneous parallel projects. And not everybody's working on the same thing at the same time. And everybody's trying to look busy, you know, and act, act busy. And it creates this incredible mass of distraction. So I would say that, that most organizations are facing those three issues to different scales and I would say we just have not. It's so new relatively, um, the whole idea of working digitally that there's a lot of mistaken assumptions, especially this idea that we need to all be looking busy all the time. And you know, because it enables such a fast pace of work, we should just like go, go, go, go, go. But if you don't actually know where you're going or on what basis you're going or who you're going with, then the go, go, go ends up just burning a ton of energy and time and not actually leading to productive output.
Speaker C: Mhm. Yeah, that was a very, very, very good point right there at the end. You basically just just explained in one sentence why burnout is on the rise and why similar issues are on the rise. And also it's interesting because all three issues the tube pinpointed here so this remoteness or, or being, not being in close contact with, with others physically, this information overload, which is itself basically very closely connected to, to more distractions. Right. Because it's usually the excess of information which distracts these all. None, uh, of these would have been possible without like advancements in digital technology. Right. So it's interesting how like in order to reap the benefits of digital technology, you have to deal with these new negative impacts that digital technologies have on your attempts on making the most out of them, I guess.
Speaker A: Right. And the people who put these technology systems in place didn't necessarily anticipate all of these kinds of issues. It all looks good on paper. It makes Sense in theory, but you know the reality when you actually try to, you know, have it roll out, play out in your organization, you encounter new problems that you had not anticipated.
Speaker C: Okay, so what exactly do we mean by transformational leadership?
Speaker A: So transformational leadership is a leadership theory. It's a theory about what really makes a great leader. And there have been a lot of different um, leadership theories over, over time, over the last century. The great man theory, that there's got to be some, typically a man, not a woman, the historic views of leadership. Who are all the historic great leaders, typically men. And that there's something uniquely special about their character that draws people to them. And that has fallen away a little bit as a main theory of leadership. But then ideas like adaptive leadership as well, just leadership theories about what is needed to make someone effective as leader. So one of the most researched of all of these theories is transformational leadership. And at least the simplified presentation that I like to focus on has four aspects, which is I uh, use the acronym VAST V A S T. So transformational leaders are vast. They put forward a vision, they model authenticity, they provide support for everyone on their team, and they transmit fully the authority and the responsibility to the people who report to them to uphold the, the goals and mission of the organization. So with the idea of vision, it is always critical for a leader to put forth. The idea of a leader is they're seeing something that others are not seeing perhaps, and they're having a courage that others may not share. And so a leader is moving towards some destination and they're moving at the front of the pack. That's by definition. And they're able to convey that vision to their team. You know, that this is what would be possible, this is what, where we're going, this is what's needed and so forth and modeling the courage to get there. The A, uh, in the VAST acronym stands for authenticity. And it's critically important that a transformational leader. The meaning of this is that a transformational leader is undergoing a personal transformation in the process of working to bring about a transformation of their people. And the personal transformation that leaders bring about is a shift away from their natural instinctive, self centered mindset to a, ah, mindset that deeply cares about all of the people on their team. And you can't be modeling that deep caring without a willingness to actually see from others points of view and stand in their shoes and actually do the work yourself in a way that's similar to what you're asking others on the, on the team to um, to do. And so that level of authenticity is critical because it's only when a leader actually steps into the shoes of others, sees things through their eyes, that the leader develops a full appreciation for how difficult it is. Right. And ideally it would be more comfortable for leaders to just stand at a distance and bark orders and you know, get angry and frustrated when things don't happen the way they are hoping that they will happen. But the authenticity aspect is that leaders really are in, in the trenches, so to speak, with the people they're trying to help and going through those difficulties. And in that sense modeling, um, having, showing that discipline of authenticity. The supportiveness deals with the generosity of leaders that they are generous with their, with all of their resources, you know, bringing whatever resources they have to bear to support the individual members of the team. But most important, importantly, they're generous in terms of caring about the individual people in their team and investing the mental energy and the time required to understand the unique needs and dispositions of everybody on their team. And so they have such a respect for the people on their team that they take the time to really understand what they need and what their challenges are and then think with them about how they can best be supported and how we can bring the resources together. And finally, the T in this vast acronym stands for transmission, which is the idea that leaders transmit the full authority and responsibility to the people that they lead. As they have grown in their capacity, then leaders step back and let others take more full responsibility. It's sort of a leader, leader model, as one of my colleagues likes to refer to it. And in the book Leadership is Language by David, uh, Marquet, he also talks about this Leader leader model. Sorry, sorry. That's um, extreme ownership, I think. Talks about leader leader model, but the idea of transmitting not just knowledge, not just instructions, but the full authority, the full responsibility implies that the leader needs to step back and give their people autonomy and freedom, which we, we know people thrive when they have autonomy. And that's a key offering of transformational leaders.
Speaker C: Mhm. Yeah. And you mentioned like one, one other keyword here is trust that you mentioned earlier. Right. And a lot of these in particular A and S, so authenticity and support. But also the last one, transmission. You know, trust is a very, very key component in all of these. Maybe not so much, I mean, vision. Yeah, it is trust of the leader in their own vision. It's not so much, you know, mutually built trust on a team. Right. So, but, but it's, it's, you know, it's, it's like it also ties to things such as psychological safety, you know, which is closely related to trust and something that's, you know, crucial for working effectively in a team culture. And especially if we return back to one of the main issues that we, that we highlighted in the intro. So this rise of remote working and remote, remote distributed, uh, maybe whether it be spatially distributed or temporarily distributed teams, trust and psychological safety become even more important. Right in those environments where it's like, yeah, we can't be face to face every day, you know, even if we are. Or, or you know, another example, we can be face to face. But, you know, I'm part of a company that got acquired by another company that got acquired by another company, you know, some time ago. And like, yeah, you know, I'm, I do work face to face with the people that are like in my original company, but I don't really have that kind of interaction with like, like the leadership of the, of the company that's acquired us, you know, so, so that's also something to consider here.
Speaker A: The trust. One thing that brings to mind when you talk about trust is, I mean, trust is a, a beautiful word. And I can, I'm, I'm visualizing, you know, one of those inspirational posters on the wall of your, your corporation talking about trust and the power of trust. And you know, we all can agree that you, uh, know, we should, we need to promote trust and so forth. But trust is not something that you can consciously just turn on or off. It's something that you feel viscerally like deep in your body towards another person or not. And it's actually, I think, a question that we need to investigate as, as individuals do I, to what degree do I trust the people around me? To what degree do I trust my leadership? To what degree do I trust my own vision and we. To accept whatever answers we, we find. Because probably there's a significant degree to which, you know, one of the things that I'm working on, uh, as a skill is delegation. And like, I hadn't fully recognized that my reluctance to delegate is a lack of trust in the people on my team that I would be delegating to that, you know, I don't think that they would do as good a job as I might. So I'm, you know, hold on to the things, you know, and that's an issue. And that's an, that's an unconscious lack of trust in my mind for those folks. And it may be correct that they, in their present state, they wouldn't be able to do as good a job as we need to do on that. And so one answer is, okay, don't delegate. Hold everything yourself and be overwhelmed. And the other answer is, okay, let's break this down a little bit. Maybe I can break the project or the challenge down into smaller parts and delegate those to the person. And also along the way giving them clear guidelines and taking the time, and this is what I mean by the supportive aspect of leadership, that you're actually investing the time to break the work down to a level that people can actually do, to explain it, to give your clear criteria for what success would be if there are problems in that work, to pro, to support people in making whatever corrections may be needed. And so, uh, it can be quite a slow process to both build trust over time and to, to take the time to figure out how to delegate the work in a way that people can understand. And I think the slowness of the process is a particular challenge for it people. Uh, I'll speak for myself because I think my brain has been rewired to think that most problems should be solved in a matter of milliseconds. And if necessary, you'll take minutes or hours to solve a problem. But most it problems are very fast moving. And so if your brain has been, you know, accustomed to thinking that problems should be solved, you know, within a few minutes or hours, these trust problems don't get solved within a few minutes or hours. These things are very slow moving challenges. Just the way that traditional projects of like civil engineering, they take months and years to accomplish. Right? So civil engineers, architects and so forth, their, their brains operate at a slightly slower cadence than it people.
Speaker C: So does this mean that transformation leadership would not be as, as good of a fit for it or, or like development teams or, or like, you know, is there just a different approach needed here or something?
Speaker A: So I mean, the, the m. The model of transformational leadership implies that the role of the leader is to create followers or followership and to become a follower, you have to change from not being a follower to being a follower. And if, if at present, as a leader, people are not naturally following your direction, then it means you also need to change. And so you know, to being a person that people will be willing to follow. And if there is no trust, then nobody will follow you, of course. So there's no way around transformational leadership if you're, if you're respond if your role in it is to guide other people. There's no way around transformational leadership in the sense that you have to change to Be the kind of person that others would follow and other people. And you have to figure out how to help them to change. What I'm saying is that most technical leaders are not necessarily. I feel like a lot of technical people were folks who fairly early in life had a fork in the road and they had the choice to either spend more time working with people or more time working with computers. And that uh, for whatever reason, they chose to spend more time working with computers because it takes a lot of time working with computers to develop technical expertise. And the thing that I like about computers, you can always debug the problem in the end, and once you fix it, it typically stays fixed unless somebody changes something. The problem with people is it's very hard to debug them. They don't have debug logs. You don't know exactly what's going on. The observability and monitoring is very low.
Speaker C: Right?
Speaker A: You can't refactor them, you can't upgrade the software very easily. People are very challenging problems, uh, compared to computers. And the most challenging problem is ourselves, right? Like we are fundamentally not linear, not rational, not as predictable as the computer systems that we like to, to imagine the world could be like so transformational leadership, uh, or any kind of leadership, any style of leadership requires for it people that they get to know themselves, they get to know other people, they get to know social interaction. And so wherever you took that fork in the road in life, you know, and stopped worrying about the messy, difficult problems of dealing with people, you got to backtrack a little bit and say, well, there's no way around this. I've got to get to know myself better. I've got to get to know people better. I've got to understand things like sociology, psychology, political science, communication, all the liberal arts stuff that you might have ignored in your early education become really important later on.
Speaker C: It sounds like it. It's in some ways even more important for technical leaders because they basically the, the skills that got them to this leadership point in their career are completely different skills in, in a lot of cases. I mean obviously a lot, a lot of people, a lot of engineers, a lot of uh, developers obviously have naturally good leadership and people skills. But you know, it, it you being a great engineer and progressing to a technical leader because of that doesn't necessitate great leadership skills. So whereas you know, in another sector it might be, you know, it might be more closely related, you know, the thing that you did previously to then managing people who are doing this. But you're still working with people, you're still working in a team. You're still, you're still kind of working on these different stuff, different things together. But if we have like the case of, you know, somebody very, very technical who is now able to work, uh, from home, who doesn't, you know, need to have face to face contact, I can imagine why, you know, doing a transformation, leadership would be even, even more beneficial and even more necessary for, for this kind of person to kind of more, more easily thrive in their new position.
Speaker A: I, I think so, yeah. This, the skills that got you here won't get you there, you know, as you say. But um, you know, both your technical skills, but also your, your strengths as an individual contributor are very different from the strengths that you need to try to be a beneficial influence on the people around you.
Speaker C: So what's, what's your way? Can you tell us a little bit about your approach, your way of, you know, providing the, this essential training to, to I guess newfound or any kind of technical leader that needs it basically?
Speaker A: Well, it's a work in progress and, and a lot of my interest in this area comes from my own challenge to figure out how can I be, you know, the most effective technical, technical leader. And so I've, I've tried to play with, you know, we, we all learn based on a current starting off point. And so the um, the starting off point that I, I think that I've been playing with is the idea of video games that when you play a video game, you can immediately step into that character, that Persona, right? Um, um, or the same if you read a book or watch a movie, something like that. We as humans just immediately identify with the main character. It's just natural, instantaneous. And you go from, you know, walking around your current environment, if you play a video game, something like that, you get you, your mind gets drawn in, your attention gets drawn into that world and you begin to treat that character as if they're. You like, oh look, I got this thing and look how, you know, high I jumped and look how, you know, oh, they almost got me right. And you start referring to that video game avatar as you. And one of the interesting, you know, and we love, you know, we love movies and books and video games and so forth because by getting into another character, we get out of this character and this character has so many problems and difficulties. Very difficult to uh, know how we can solve all the problems of this character. The character that we play most of the time, the avatar, the role that we're playing you know, in our 9 to 5 job, we really need a break from that person's problems. And so, you know, getting into the problems of some, ah, other character just feels like an enormous relief, um, when. But it's really interesting to think about when you're looking at a video game character, whatever. There's, there's a, there's a distance and there's a freedom that we often don't feel that we have in our present life. Like, you can see what's going on around that character. You know, you can see it a little bit from the outside. You can see maybe incoming dangers and you have a chance to redo things. Things, you know, you die on one level and you redo it. You know, you know, you get another life and you come back and you, you do it. And so there is this character of experimentation and playfulness and gamification that I think we don't really have in our normal life. A lot of the time we feel like we're just stuck in a particular job, stuck in a relationship, stuck in a, you know, body, certain, you know, whatever health issues. And so we feel very stuck in our current identity. And we don't feel that sen. Of distance and playfulness and so forth that you, you feel when you're playing a game. And so the, the approach that I'm building a leadership training program and based around this approach of just stepping back a little bit and like, looking at the game of our life and trying to take more of a playful approach to the game of our life and understand who's the, who's the big boss at the end that we're trying to work up to, you know, tackling that and what are the little obstacles we have to get through and what are all the dynamics of the game. And also, so just knowing that there's this learning process, we can go through this learning process, continual change. And there's six practices that I took. I had, um, my background prior to becoming, going full time into it. I'd spent 15 years as a Buddhist monk and so training in that context. And so all of the, all of the practices that we did in that context, we organized into six practices. Giving moral discipline, patience, joyful effort, concentration and wisdom. And I don't have six fingers. I can't point all of them. And there's an expression from giving comes wealth. That's a little bit paradoxical. From giving comes wealth. But the main purpose of. In all of our companies, in the business context is the companies. People join a company because they'll get paid and hopefully, uh, ideally you have a good time at work, but most of us wouldn't be doing exactly this job in exactly this way if nobody was paying us. But you're not going to keep getting paid unless the company keeps getting paid, right? And so the company's financial health is, you know, is critical, you know, for the long term job stability of everybody in the company. And to the degree that we're doing this job because, you know, we have to, to get paid to, you know, then the financial health of the company becomes critically important. And so when we want to think about how do we help the company to be financially successful, how do we help bring about wealth for the company, for the organization, the key there is giving. And when, when I say giving, I mean we're giving our care, our attention, our time, our skills. We're giving to our coworkers, we're giving to our customers, we're trying to give to shareholders, we have investors and we're ideally, you're in an organization, a business that's giving to society, right? And so this mindset of how can we give skillfully and how can we train ourselves to, to take everything, to take an attitude of generosity that long term is what will end up with us being more successful financially and uh, in other ways as an organization, of course, it's not meant to be reckless. You know, I mentioned these six practices. The last of them is wisdom. So you need to be giving with wisdom. And that wisdom part is really where the playfulness comes in, in the scientific approach where you're experimenting, you're understanding, you're trying to deepen your understanding of the financial dynamics in the organization, the social dynamics in the organization, the technical dynamics in the organization. Our organizations are very, very, very common, complex customers are complex and changing, ever changing employees are changing. Everything's complex, right? And so the big challenge is how do you build the wisdom to understand how to skillfully approach your day at work with a mind of generosity that you're, that even if you're in a role of, as a salesperson, right? And your, your, your job is to collect money for the company. You need to be going in with an attitude of giving rather than taking. You want to be able to, you want to connect with a customer and give them through your organization so much benefit that they, it's a small sacrifice for them to part with some money, you know, in, to compensate you for the value that you've brought, right? So everybody in the organization, from sales, through support, and they need to be taking this attitude of, of generosity, but a wise generosity, skillful generosity. So that's kind of the summary of the program.
Speaker C: Yeah, I mean, I mean, me or us being better off doesn't necessitate somebody else having to be worse up, right? We can all be better off. It does. It's not an either or. It's. It can be a both. And man. Man. I was thinking this conversation was actually suspiciously spiritual. I love it. Okay.
Speaker A: I felt really, uh, I'm kind of coming out of the closet as a spiritual person. I felt really quite, uh, uncomfortable, awkward about even though using the word spiritual in a business context because we've had, you know, a long history of trying to kick religion out of the workplace, and religion and politics, kick them out of the workplace, the two most contentious topics, so that people can just work together because you need a collaborative, harmonious workplace. Um, and so spirituality, of course, nothing to do or very little to do with religion, but it's. I think about spirituality as like the, the levels below the conscious, you know, what's going on in our body, what's going on in deep emotional levels. Spirit, meaning. Meaning like breath. Like, what is. What is driving our breath? What is driving our life force, life energy at a deep level. Like, why do we wake up? Why do we do things or not do things? And that, that whole learning journey of really understanding what's this, what's. To use a technology term, what's the stack, you know, on which our conscious existence is. Is. Is operating, you know, and we've got to debug the stack on which our conscious experience is operating if we want to really be maximally effective, individually or
Speaker C: collectively, debug the stack of our consciousness. I love that, Andrew. Let's talk about this more on some other conversation. But I love the topic and I love today's conversation with you, Andrew, a really, really great one. If, if anybody listening right now is interested in learning more about you, learning more from you, connecting with you, what's the best ways to reach you? Where should they contact you?
Speaker A: LinkedIn is pretty much the only social media channel that I'm active on because it's the only social media platform that's boring enough to not be addictive. So hit me up on LinkedIn. I'd love to connect. Yeah. And you can find out more about my other activities and auto rabbit and so forth there.
Speaker C: Oh, yeah, you also have a podcast with, uh, Steve Wright. It's a flow engineering podcast.
Speaker A: That's right. So Steve Pereira and I wrote or co authored this book, Flow Engineering we have a podcast in the early days, but we've got episodes out at least every couple of weeks.
Speaker C: Cool. So we'll make sure to link that as well, as well as like, uh, an Amazon link to your book. And yeah, thank you again. As I said, this has been great. I really enjoyed having you as our guest today.
Speaker A: Great pleasure.
Speaker C: Nice to be with you, Tim, and to our listeners. That's all for this episode. Have a great day, everyone, and stay safe.
Speaker B: Thanks for tuning in. If you'd like to check out our other episodes, you can find all of them@agildrop.com com podcast as well as on all the most popular podcasting platforms. Make sure to subscribe so you don't miss any new episodes, and don't forget to share the podcast with your friends and colleagues.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.