This is one of a series of case studies documenting how shapeshifters navigate real professional challenges. Names and details are shared with permission.

Summary

Ashish Chopra is an Indian-Australian data professional who spent five years in a company while it moved from the late start-up stage to a more mature scale-up. Through multiple rounds of change in the organisation, he retained the quality that made him valuable from the start: deep flexibility. He absorbed whatever was needed: reactive high-stakes work, large cross-company projects, mentoring, filling gaps. The organisation kept calling on him for exactly that.

Yet with this came a tension. The problem wasn't that his work had outgrown his title. It was that the organisation had grown a skeleton around him, and the more formal structure had no anatomical category for what he did: something like cartilage or fascia, a critical soft tissue elastic enough to hold thing together. Bands, layers, headcount: these HR categories are the language of bone. What Ashish did was something different: connective, adaptive, load-bearing in ways that don't show up on an org chart. His performance reviews were always excellent, but the new formal structures that were evolving in the company had no clear language or model for what he was doing.

What the Shapeshifters framework did was allow him to formalise the informal, and give his organisation a way to see and name what had always been there, and valued.

The Situation

After a few years in the company, Ashish had negotiated an atypical title as Insights Lead. The role had been designed around a proactive function: generating and surfacing insights for the business. In practice, his most valuable work was reactive. He would be pulled into high-stakes projects at short notice, work across functions on problems that had no clear owner. He was good at this, and found it meaningful. But, he carried a quiet anxiety that someone might point at his job description and note that he wasn't doing what it said.

Over this period, three tensions had been accumulating:

• In the context of developing more formal and regular structures, HR started questioning why someone at his salary level had no direct reports
• Colleagues couldn't easily place his work against his title, especially newcomers who didn’t have a long experience of observing his work.
• Peers from his starting cohort had moved into people management, the conventional signal of advancement. Reporting to them seemed somewhat off.

Underlying all this was a language or a mapping problem. The organisation didn't have the words and model for what he was doing. People saw it, including at the very top, but the structure didn’t.

What he did

Ashish came to work with the Shapeshifters Group at a moment of organisational change. There was a restructure that brought under a new manager – someone who had already worked productively with him, and valued him. With this came a chance to renegotiate.

Using the shapeshifter competency framework, Ashish mapped what he actually did: work across functional boundaries, hold the analytical continuity on large cross-company projects, or be called in at moments of high-stake urgency to deliver ‘good enough’ on the near-impossible. The framework gave him precise language for the pattern he had been living.

He wrote a new job description. It gave a clear, descriptive, honest account of his work as it was, using simple vocabulary that could be

He first brought it not to HR, but his new manager, who understood what it meant to hold an organisation together from the middle. The manager read it, and showed immediate recognition: "That's exactly what I do, and what two of my other reports do."

They refined the document together. It went to HR as a shared proposal. HR approved it.