Connective Blog

Software Development Is Becoming Positionless Basketball

There was a time when you could tell exactly what someone did on a basketball court just by their number.

The 1 brought the ball up.  The 2 shot.  The 3 slashed and defended.  The 4 battled inside. (Me, smaller but mean)   The 5 protected the rim.

You stayed in your lane. That was structure. That was discipline.

And then the game changed.

Teams like the Golden State Warriors started winning championships with lineups where everyone could dribble, pass, shoot, switch on defense, and read the floor. The traditional labels still existed, but they mattered less. What mattered was whether you could play the game in front of you.

The smartest players became the most valuable, not because they scored the most points, but because they understood spacing, timing, momentum, and how to create advantages.

Software development is going through that same transformation right now.

For years, teams were structured like old school basketball. Frontend developers wrote UI. Backend engineers handled APIs and data. QA validated. Product managers wrote requirements. Cloud engineers managed infrastructure. Everyone had a defined role and a predictable handoff.

It worked, as long as the game moved slowly enough.

Then AI entered the court.

Today, code can be generated in seconds. Test cases can be written automatically. Documentation can be drafted instantly. Architecture patterns can be suggested on demand. Agents can analyze logs, refactor functions, and even propose product enhancements.

When machines can produce the shots, the human value shifts.

The question is no longer, “Who writes this line of code?”  The question becomes, “Are we solving the right problem?”

Engineers who once differentiated themselves by output now differentiate themselves by judgment. They have to understand the business context, the tradeoffs, and the long term implications of architectural decisions. If AI can write most of the code, the thinking becomes the real competitive advantage.

At the same time, product managers and product owners cannot operate purely at the requirements level. When execution cycles compress, shallow technical understanding creates friction. The best product leaders now need to understand system constraints, data models, integration realities, and the limits of AI tools. Otherwise, they are drawing plays that cannot be executed.

This is positionless development.

It is not that roles disappear. It is that the edges blur.

The best engineers think like product strategists.  The best product leaders think like technologists.  AI becomes a force multiplier for teams that know how to orchestrate it.

But here is the tension. Most organizations are still built for the old game.

Job descriptions assume narrow specialization.  Delivery models depend on sequential handoffs.  Performance metrics reward volume over impact.  Governance structures were not designed for AI accelerated iteration.

Teams feel the friction. They sense the shift. They know the game is speeding up, but they are still running old plays.

This is where operating model becomes strategy.

At Connective Consulting, we spend our time in the space between business ambition and technical execution. We do not just help clients build software. We help them rethink how software gets built and how teams are structured to win in this new environment.

Positionless development requires more than adopting AI tools. It requires aligning leadership, product, engineering, and governance around outcomes. It requires redefining what good looks like in performance, in hiring, and in collaboration. It requires raising the bar on strategic thinking across the organization.

The companies that thrive in this next phase will not be the ones with the most specialized roles.

They will be the ones with adaptable teams who understand the whole court. They understand the business model, the customer journey, the technical architecture, and the leverage AI provides.

In basketball, positionless play did not eliminate skill.

It demanded more of it.

Software development is entering that same era.

The labels still exist. But the advantage belongs to the teams who can play the game, not just their position.

Hannah Stork is a technology sales leader and strategist with experience helping organizations translate software, AI, and digital transformation into measurable business outcomes. She works closely with executive and IT leaders to bring clarity to complex initiatives, modernize digital capabilities, and turn AI and software investments into measurable impact. Outside of work, she enjoys golfing, cooking, and spending time with her two kids.