|
Please forward this to a high-impact leader who needs the energy edge. If this was forwarded to you, get plugged in here. Welcome back - it's nice to have you here! Before we dive in... I remember the desktop computer at my first job out of college. Not a laptop. A desktop. When I left the office, the computer stayed there. But that wasn't even my first experience with how quickly technology could change. Before college, I had one of those cow-print Gateway 2000 computers at home. If you remember those boxes, you know exactly what I'm talking about. π I grew up with dial-up internet, watched high-speed connections become normal, and eventually found myself carrying more computing power in my pocket than I could have imagined back then. And now I'm building custom AI agents to support parts of my work that didn't even exist when I started my career. Quite a few upgrades along the way. But here's what interests me more than the technology itself. None of those changes waited for us to finish learning the previous version. The tools changed. The expectations changed. Eventually, the work changed. And most of us were busy doing our jobs while it happened. π― THE MOMENTI've been thinking about this more as I spend time with high school and college students. Last April, I visited Suffolk University as part of its Professional in Residence program. I've had the opportunity to return several times, and I always enjoy hearing how students are thinking about careers, entrepreneurship, and what comes next. During that April visit, something caught my attention. In the particular classes I met with, roughly half the students had already started some kind of business. Some had begun in high school. Others had started during their first year or two of college. About half. I don't know how representative that classroom was of students everywhere. But it certainly challenged an assumption I'd carried from my own early career. For a long time, the familiar sequence looked something like this: Get educated. Find a job. Build experience. Develop expertise. Maybe, eventually, start a business. These students were already experimenting with the last part while still working through the first. They weren't necessarily waiting for a degree, an employer, or a certain number of years of experience to give them permission to try. And I found that fascinating. Not because everyone should become an entrepreneur. They shouldn't. But because the sequence itself is changing. The barriers to building something, testing an idea, finding an audience, or learning a new skill are different from what they were when I started my career. That doesn't mean the work is easy. It doesn't mean experience or education have lost their value. It means people can begin discovering what they're capable of before the traditional system says they're ready. And it raises a question I've been carrying into my work with founders, executives, and leaders. What happens when the world changes faster than the systems we've built to prepare people for it? β‘ QUICK SPINThe job can change long before the curriculum, job description, or training program catches up. And there's an uncomfortable contradiction in that. We spend years developing expertise. We earn credibility because we know what we're doing. Then something changes, and we're asked to become beginners again. Sometimes we resist. Sometimes we don't even notice that we're resisting. We keep doing what has worked because, well, it has worked. But yesterday's competence isn't always enough for tomorrow's conditions. The challenge isn't knowing everything that's coming. It's staying curious enough to recognize when what you know needs updating. π οΈ MY TURNI see this in my own business all the time. What helped me get started five years ago isn't automatically what will help me grow from here. That's true of how I coach, how I build relationships, how I produce my podcast, and how I think about the systems supporting the business. And AI has made the distinction particularly visible. When I started experimenting with tools like ChatGPT and Claude, I could have treated them as another piece of software. Open the tool. Ask a question. Get an answer. There's plenty of value in that. But after using them for a while, I realized I was approaching the problem too narrowly. I didn't simply need better answers. I needed to think about how the tools fit into the way I actually work. What context was missing? What did I keep explaining over and over? Which processes were already effective? Which ones needed to change before adding another layer of technology? That curiosity eventually led me toward building custom AI agents around my own work. And even that isn't a finished system. I'm still experimenting, adjusting, and figuring out what deserves to become part of how I operate. Some things work. Some don't. Some look exciting for about fifteen minutes until I realize they don't solve a problem I actually have. That's part of the process, too. I don't believe the answer is to spend every available hour chasing the next tool, trend, or capability. We'd never get any actual work done. But I do believe we need to give ourselves permission to explore a corner of something unfamiliar. To see what it does. To question whether it changes an assumption we've been operating under. And then decide whether it belongs in the work. There's a difference between adopting a new tool and adapting the way you work. One adds something to the system. The other asks whether the system itself still makes sense. π THE BACKUPThere's a tension here that goes well beyond technology. We tend to think of competence as something we accumulate. We learn. We practice. We get better. Eventually, other people trust us because we've demonstrated that we know what we're doing. That's a good thing. But competence can also make the unfamiliar feel more expensive. If you've spent five, ten, twenty, or more years becoming the expert in a particular area, starting from scratch in another one may not feel especially appealing. You know what good work looks like. You know how to get results. You know how to avoid mistakes. And now you're supposed to experiment with something you don't fully understand? Wonderful. Just what your calendar needed. But consider the alternative. What happens when the assumptions supporting your expertise begin to change, and you don't notice? Or you notice, but decide to wait until someone else tells you what to do? This is one reason I've become increasingly interested in the relationship between personal agency and the systems around us. We often talk about education and professional development as though learning happens in a separate place. A classroom. A course. A conference. A training session. Then we return to work and apply what we learned. There's real value in those structures, especially where formal knowledge, professional standards, and safety matter. But some of the most important learning happens when we encounter something our existing knowledge doesn't fully explain. A customer behaves differently than expected. A process that used to work starts creating friction. A younger colleague approaches a problem in a way we hadn't considered. A new technology makes something possible that previously required an entire team. Those moments aren't interruptions to learning. They are opportunities to learn. And there's another layer worth noticing. We can become so comfortable with the way our organizations operate that we stop asking whether those systems still serve the people using them. AI is a useful example. If a company has a confusing approval process, unclear responsibilities, or a habit of producing reports nobody reads, adding AI doesn't automatically improve the underlying design. It may just make it easier to generate more reports, move more information, and scale the confusion. The technology might be new. The assumption that the existing process deserves to survive may be very old. That's why curiosity matters before implementation. Not every new capability deserves adoption. And not every established practice deserves protection simply because it's familiar. π οΈ THE SYSTEMSo where does that leave us? I think we need to separate two things we often combine. Giving ourselves permission to explore. And finding the permission needed to experiment within the systems where we work. They're related, but they're not the same. The first is personal. You notice something changing. You become curious. You decide it's worth understanding, even if nobody has assigned it to you. You don't need your manager to authorize the thought. You don't need a new job description to ask a better question. You don't need to know whether an idea will succeed before you're allowed to wonder about it. But bringing that curiosity into an organization can be different. Now you're dealing with shared priorities, customer expectations, data, budgets, colleagues, and the realities of getting work done. That's where systemic permission matters. And I think we sometimes skip the conversation that connects the two. Imagine someone going to their manager and saying: βI've been exploring something that might improve part of how we work. I don't know yet whether it's right for us, but I'd like to understand it better. Could we figure out a small, responsible way to test it?β I like that conversation. There's no grand claim that the new idea will revolutionize the business. No demand to throw away the existing process. Just curiosity, initiative, and a willingness to find out. Now imagine you're the manager receiving that request. You might have legitimate reasons to say no to a particular experiment. Maybe the timing is wrong. Maybe the proposed tool creates a security concern. Maybe the team needs to finish something more urgent first. Those are real considerations. But there's a difference between setting responsible boundaries and treating uncertainty as a reason not to explore at all. A leader can say: βNot with customer data. But could we test it with a fictional example?β Or: βWe can't change the whole process right now. What part could we examine first?β Or even: βI don't see the application yet. Show me what you're noticing.β Those responses don't guarantee an experiment will work. They make learning possible without pretending the organization has unlimited time or resources. And they send an important signal. Curiosity is welcome here. Not because every idea is brilliant. Because people who notice change and responsibly investigate it help the organization remain capable of changing, too. Try this in your next conversation...If you're an individual contributor, bring one observation rather than a fully formed proposal. βI've noticed something about how this work is changing. Could I walk you through it?β If you're a leader, try asking: βWhat have you noticed changing in our work that we haven't made room to explore yet?β Then listen. You may discover a useful idea. You may discover a process that needs attention. Or you may discover that someone on your team has been curious about something for months but assumed they weren't supposed to bring it up. The conversation is the beginning. What you make possible afterward is what matters. π‘ THE SHIFTWe've built a lot of our professional lives around the idea that learning prepares us to work. Study first. Qualify second. Perform third. And in many situations, that sequence is essential. But the sequence isn't the whole story anymore. Because the work itself keeps changing. The founder who built a business around one set of assumptions eventually encounters a different market. The leader who succeeded by personally solving every problem eventually needs to develop other people's judgment. The parent who knew exactly how to help a young child eventually has to learn what support looks like for a teenager. Different situations. Similar challenge. The approach that worked before may still contain something valuable. But it may no longer be sufficient on its own. That's not a failure of experience. It's a reminder that experience is something we bring into the next situation, not a guarantee that the next situation will behave like the last one. And maybe that's the real opportunity. We need to learn within the work, not work to learn. Not because formal education or training no longer matters. Because learning doesn't stop when the formal preparation ends. It becomes part of how we notice, decide, lead, and adapt. Personal permission opens the door. The systems around us can either help us walk through it or make the doorway unnecessarily difficult to use. Both matter. π§ THE PERMISSION-TO-EXPLORE LOOPReady for a very practical way to turn curiosity into something useful without making learning another enormous obligation on your calendar? 1. NOTICE: What's changing around me?Look for something that no longer behaves quite the way you expect. A customer need. A new tool. An outdated assumption. A process creating more work than it should. You don't need to understand the change completely. Start by noticing it. 2. PERMIT: What can I give myself permission to explore?Choose one question worth investigating. Not an entire industry. Not every AI tool released this week. One small area where curiosity might reveal something useful. You can explore an idea without promising that it will become part of your work. 3. PARTNER: Whose support would make a responsible experiment possible?If your exploration affects colleagues, company resources, information, or existing commitments, bring the right people into the conversation. Ask what boundaries matter. Ask what a reasonable test might look like. Don't confuse seeking support for an experiment with needing approval to be curious. 4. PRACTICE: What's the smallest test that could teach me something?Try it. Observe what happens. Did it solve a real problem? Did it create a new one? Did it challenge an assumption? Did it simply confirm that your current approach works better? All of those outcomes can be useful. The point isn't to prove every new idea deserves a place in your operating system. It's to keep that operating system capable of learning. Try this before FridayThink of one thing you've noticed changing in your work. Write down the assumption you currently hold about it. Then ask yourself: βWhat small experiment would help me find out whether that assumption is still true?β You don't need to reinvent your career by Friday. You might just discover one part of your work that's ready for a different approach. Don't wait for permission to be curious. Find the permission you need to experiment. π€ YOUR TURNThink about something you've been curious about lately but haven't explored because it falls outside your role, training, or usual way of working. Are you waiting because the system has actually said no, or because you haven't yet given yourself permission to ask? Those are two very different obstacles. And they may require two very different next steps. π LET'S TALKThis is a big part of how I think about Transition Leadership. The operating system that helped you succeed at one stage of your career, business, or life isn't automatically the one that will support the next. But that doesn't mean you need to discard everything you've built. Experience matters. Relationships matter. Judgment matters. The challenge is recognizing which parts of your approach are still serving you and which ones have become assumptions you're no longer examining. In my coaching, I'm interested in the conditions underneath that transition. What changed? What are you still doing because it used to work? What are you curious about but haven't made room to explore? And what would it take to build a more intentional system around where you're going? That's where Transition Leadership and EnergyOS come together for me. Not in chasing every new possibility. In creating enough awareness, capacity, and agency to choose which possibilities deserve your attention. π adamwbarney.comβ Cheers, Adam P.S. I sometimes wonder what the younger version of me, sitting in front of that cow-print Gateway 2000 computer, would think about the AI tools I'm building today. Probably something along the lines of, βWait, you can do WHAT?β And I suspect a few years from now, I'll be asking myself the same question about whatever comes next. π STAY PLUGGED INThis week's Is Anything Real? conversation takes us somewhere a little different. Wine. Yes, wine. π· In Episode 86, βSave Wine Night: PureWine, Wine Sensitivity, and the Father-Son Invention Story,β I sit down with David Meadows, PhD, and his son Derek Meadows, the team behind PureWine. Their story begins with a familiar problem. For some people, enjoying a glass of wine can come with unwanted discomfort. It's easy to accept that as an unavoidable trade-off. Enjoy the wine and deal with the consequences, or stop enjoying the ritual altogether. David and Derek became interested in whether there might be another approach. That curiosity led them into the science, product development, and challenges of building a business around wine filtration. And the part that connects to this week's newsletter isn't whether you drink wine or need their product. It's the decision to question an assumption that other people may have stopped examining. The episode also explores how difficult it can be to introduce something new when customers already have an explanation for the problem. That's an interesting challenge for any founder. Inventing something is one kind of work. Helping people reconsider what they believe is possible is another. Sometimes adaptation starts with a new technology. Sometimes it starts with a student building a business before graduation. And sometimes it starts with a father and son asking whether a familiar experience could work differently. Different starting points. Same willingness to explore. This episode is for wine lovers, holiday hosts, product builders, founders, gift-givers, and anyone who's wondered whether there's a better way to enjoy the rituals that bring people together. A little something extra: If you're curious about PureWine, use code ABARNEY20 for 20% off your first order at drinkpurewine.com. Was this valuable? Hit reply with a β or β. I read every one. |
A weekly field guide to the invisible forces shaping ambitious lives and leadership. Every Monday, explore the patterns shaping your energy, decisions, identity, performance, and how you lead...so you can see them, name them, and choose what happens next.
Please forward this to a high-impact leader who needs the energy edge. If this was forwarded to you, get plugged in here. Welcome back - it's nice to have you here! Before we dive in... Someone goes quiet during a difficult conversation. What do you assume? That they're thinking? Upset? Avoiding the issue? Trying not to make things worse? Or that they simply don't care? Now reverse the situation. You're the one who goes quiet. You know you're listening. You know you're processing. You may...
Please forward this to a high-impact leader who needs the energy edge. If this was forwarded to you, get plugged in here. Welcome back - it's nice to have you here! I don't usually send emails like this, but here we are. π I've made it into the Top 5 of the Top Host competition, and I'm currently sitting in 2nd place. Here's the catch: only the person in 1st place advances to the Quarter-Finals this Thursday. If you've been following my journey with Is Anything Real?, you know this whole...
Please forward this to a high-impact leader who needs the energy edge. If this was forwarded to you, get plugged in here. Welcome back - it's nice to have you here! Before we dive in... I can still picture a conference room from my early agency days. We were trying to solve a client problem. One issue. One meeting. A room full of people doing their best to get it right. Then another email came in. And another. And another. Within roughly 30 or 45 minutes, we'd received something like six to...