The biggest advantage you can have right now is being obsessed. Or at the very least, giving a shit. That's the moat. Not frameworks, not credentials, not a particular stack or methodology. Just caring an unreasonable amount about how things work and why. In a landscape where everyone has access to the same tools, the same tutorials, the same AI assistants, the differentiator isn't what you know. It's how much you care about what you don't know yet.
The secret, if there is one, is oscillating between half-in-the-bag and full psychosis. Somewhere in that range is where the good work lives. You're reading everything. You're breaking things and rebuilding them. You're staying up too late because you saw something that completely rewired how you think about a problem you've been circling for weeks. That's not burnout. That's momentum. And right now, momentum is the whole game. The people who are coasting, waiting for clarity, waiting for the dust to settle before they make a move, are going to find that the dust doesn't settle. It just becomes the new atmosphere. You either learn to breathe in it or you suffocate.
The ground is shaking
We're in a transitional period. The ground is shaking under all of us, and what previously worked, the playbooks, the frameworks, the career ladders, none of it maps cleanly to where things are headed. The assumptions baked into how we've been working are expiring in real time. You can feel it in the way teams are being restructured, the way products get shipped, the way entire job descriptions are being rewritten or quietly eliminated. The rules that governed how we built software, how we organized teams, how we measured productivity, those rules were written for a world that no longer exists. We're living in the lag between the old operating system and the new one, and most people haven't even acknowledged that the update is happening.
And that's fine. That's actually where the opportunity lives.
The more you care about what's happening, not just in your lane, but across the whole landscape of how things get built, the more prepared you'll be in the long run. Curiosity compounds. Apathy decays. The people who are going to thrive through this transition aren't the ones with the best résumés or the most polished case studies. They're the ones who can't stop pulling on threads. They're the ones who look at a new tool and don't just ask "how do I use this?" but "what does this make possible that wasn't possible before?" That second question is the one that matters, and it's the one most people skip because the first one is easier and more comfortable.
The magic box got weirder
Computers have always been the original magic box, an S-tier transformer. You put something in, something wildly different comes out. That's been true since the command line, and it's even more true now. The box just got weirder and more powerful. What used to require a team of engineers and a quarter of runway can now be prototyped in an afternoon by someone with taste and enough technical fluency to know what to ask for. That shift is seismic. It doesn't eliminate the need for deep expertise, but it radically compresses the distance between an idea and something real. The people who understand what the box actually does, not just how to operate it, are the ones who'll shape what comes next. There's a meaningful difference between using a tool and understanding the physics of what it makes possible. That gap has never mattered more than it does right now.
Design's identity crisis
This is especially true for designers. I think this is where a lot of teams, and a lot of designers in particular, are getting tripped up. In this new age of work, it's critical to hard-frame around what the value of design is versus what design actually does day to day. These are two different things, and we collapse them together way too often. We confuse the motions of design with the meaning of it. We mistake the ceremony for the substance.
Too often, we get caught up in the tasks. The steps, the rituals, the artifacts. We fetishize the process instead of interrogating whether the process is still earning its keep. We run the same sprints, attend the same standups, produce the same deliverables, and never stop to ask whether any of it is moving the needle or just making us feel productive. It's the same trap as being a "user of tools" when what you should be is someone wearing a belt of accessories, choosing what to reach for based on the situation, not running a script someone else wrote five years ago. One posture is passive. The other is deliberate. One makes you replaceable. The other makes you indispensable.
Process is a vehicle, not a destination
We don't want fixated process. We don't want schemas that further abstract something that is, by nature, always evolving. The SDLC doesn't need to be preserved like a museum piece. Scrum is not sacred. Agile, as most companies practice it, has become the very bureaucracy it was invented to escape. These were vehicles, not destinations, and the road has changed. When you cling to a process because it's familiar rather than because it's effective, you're optimizing for comfort at the expense of outcomes. And in a moment like this one, comfort is expensive.
The goal of a business is to ship and to develop. To move ideas into the world and learn from what happens when they land. That's the fundamental loop. Everything else, every process, every framework, every methodology, is supposed to be in service of that loop. Design's value is in making that movement smarter, faster, and more aligned with real human need. It's in asking the right questions before the wrong thing gets built. It's in making complexity feel simple and making the invisible visible. That's the contribution. That's what earns a seat at the table. Everything else is overhead until proven otherwise.
Outcomes over optics
The problem is that proving otherwise requires honesty that most organizations aren't comfortable with. It means looking at your rituals and admitting that some of them exist because they always have, not because they work. It means being willing to kill a process that took months to establish if the evidence says it's slowing you down. It means valuing outcomes over optics, which sounds obvious until you realize how much of modern product development is organized around looking productive rather than being productive.
For teams that can afford to operate this way, stripping back to the essential loop of build, ship, learn, great. But it's not a default you drift into. It's an active commitment. You have to be willing to let go of the process that made you feel safe in exchange for the process that actually works right now. That takes trust, both in yourself and in the people around you. It takes a willingness to be wrong faster than you used to be right. It takes the kind of intellectual honesty that makes people uncomfortable, because it means admitting that the thing you spent years mastering might not be the thing that matters most anymore.
Stay close to the work
And "right now" keeps changing. That's the part that makes all of this feel unstable, but it's also the part that makes it exciting if you let it. The half-life of any given best practice is shrinking. What worked six months ago might be dead weight today. The only sustainable strategy is to stay close to the work, stay close to the tools, and stay close to the problems. Not from a distance, not through dashboards and decks, but hands on, in the mess, building and testing and iterating with the kind of intensity that only comes from actually caring.
Which brings us back to the beginning. The advantage is obsession. The advantage is caring enough to keep recalibrating, to notice when the ground shifts and adjust your footing instead of pretending the floor is still level. The people who treat this moment like something to survive are going to get lapped by the people who treat it like something to explore. The ones who lean in, who stay curious, who refuse to let their process calcify around them, those are the ones who will define what good work looks like on the other side of this.
Stay a little unhinged about it. That's the move.