For a long time, I honestly believed that good judgment and sustained effort could push almost any situation forward. In most unfinished roles, that belief held up, and it shaped how I worked.But it didn’t work universally.What follows are the places where that assumption broke down, and what I learned in situations where despite responsibility and good intent being present, the surrounding conditions set hard limits.When Effort Isn’t the ConstraintEarly in my career, I treated forward motion as its own kind of proof. If progress stalled, my instinct was to assume I hadn’t yet learned enough, pushed hard enough, or adapted fast enough.Often, that instinct served me well. It pushed me to close gaps quickly, take ownership, and stay engaged when things were uncomfortable. But not always.There were roles where responsibility was real, trust was extended, and judgment was exercised, but outcomes remained uneven. Not because no one cared, or because the work lacked effort, but because the conditions surrounding the work had imposed limits that individual judgment alone couldn’t overcome.In some cases, the gap wasn’t diligence, it was fit. The role required a kind of contribution that didn’t align cleanly with how I operate or demanded a level of specialization that took longer to develop than the situation allowed.Those gaps weren’t always obvious at the outset. In unfinished roles, boundaries and expectations often become visible only after momentum is already underway. By the time misalignment surfaces, responsibility is shared and unwinding it isn’t simple.Structural Limits Don’t Yield to JudgmentI’ve also seen situations where the constraint wasn’t personal at all. It was structural.Some organizations want clarity without allowing the disruption required to produce it. Others expect momentum while withholding decision authority. In those environments, judgment can slow loss, but it can’t manufacture conditions that don’t exist.That distinction mattered. It forced me to separate problems that yield under pressure from those that don’t move no matter how much effort is applied.Early on, I treated both the same way by pushing harder.Over time, I learned to watch for different signals: repeated decision stalls, ownership that remained ambiguous despite escalation, and sponsorship that weakened as complexity increased. Those patterns didn’t always show up loudly, but they were consistent.Recognizing them didn’t make the work easier. It made it more honest.Changing Too Many Variables at OnceOne of the clearest lessons here came when I left Microsoft in 2014 to join Parallels.I was deliberately trying to replicate patterns that had worked well for me inside a large, well‑resourced organization—this time in a much smaller company. The role looked like an opportunity to apply judgment and operating discipline in a leaner environment, where impact could be more direct.It was also my first fully remote role. I was based in Seattle, working closely with an engineering team in Moscow. I traveled frequently, believing that trust and shared context couldn’t be built entirely at a distance, especially across time zones, oceans, and cultural boundaries.What proved harder than I expected was even defining the audience I was supporting. It wasn’t clearly defined or quantifiable. Expectations existed, but they weren’t anchored to a shared understanding of who the work was ultimately for or how success would be measured.At the same time, the underlying technology was complex and unfamiliar to me, which meant part of the job was building enough technical fluency to even recognize what the audience needed before determining how to meet those needs.Individually, I made reasonable moves: traveling to close gaps, adjusting how I communicated, building context, and pushing for clarity where I could.What I hadn’t fully accounted for was how many variables I’d changed at once.A former Microsoft executive once shared a simple rule that stuck with me: when changing jobs, there are three legs to the job stool: role/discipline, location, and technology. Ideally, you should only change one at a time, but you really shouldn’t change more than two. I changed all three, confident I’d figure it out the way I had before.What I underestimated was how much of my effectiveness had been grounded in knowing how work actually gets done at Microsoft—how decisions move, where leverage exists, and which paths matter. That context had been doing more work for me than I realized.By the time I saw that clearly, the organization itself was already in motion, and the window to course‑correct was closing. One year into the role, our division was sold to another company. Months later, the acquiring company laid off my role and many others outside of engineering and support.Even if I had recognized it sooner, it likely wouldn’t have changed the outcome. But it did change how I evaluate risk, readiness, and whether effort is likely to compound in each context.Learning to Name the BoundaryOne of the harder lessons was learning to distinguish between:- a temporary lack of clarity that yields under pressure, and- a persistent constraint that doesn’t move, no matter how much judgment or effort is applied.That distinction added a corollary to the core question of “How do I push this forward?": _“Which parts of the system are not configured to move, regardless of effort?”_There’s a kind of realism in that shift; not resignation, but calibration. Not everything yields to persistence, and not every environment rewards judgment in the same way.Judgment Includes Exit ConditionsFor a long time, I thought good judgment was mostly about endurance: staying engaged, absorbing pressure, and continuing to move.Experience added a second dimension: discernment. Knowing when continued effort is compounding learning, and when it’s merely extending friction.That doesn’t mean walking away at the first sign of resistance. Ambiguous work is supposed to be uncomfortable. But there’s a difference between productive strain and structural drag and confusing the two carries a quiet cost on the work, the team, and the person carrying the load.Some of my clearest lessons came not from successful outcomes, but from situations that resisted resolution. Those moments sharpened my understanding of fit, context, and the kinds of environments where this way of working can and can’t sustain forward motion.Carrying the Pattern ForwardLooking back, operating without a playbook sharpened my judgment by putting it under stress. Learning its limits gave that judgment some shape.It made me more attentive to context, more explicit about constraints, and more willing to name misalignment rather than absorb it silently.If there’s a throughline across these experiences, it’s this: responsibility accelerates learning, but wisdom comes from knowing when responsibility alone isn’t enough.That distinction is what I carry forward now not as caution, but as calibration. Judgment still matters most in motion, but motion itself isn’t the goal.Meaningful progress is.Photo by Brian Kelly on Unsplash