The person who knows a software tool best is not always the person who helps a firm use it well. Randy Deutsch used the term super user for a broader combination: curiosity about tools, confidence to experiment, capacity to learn, creativity to connect tools, and the interpersonal skill to bring other people into the work.
That combination can be difficult to see on an organization chart because it crosses the lines between technology, design, process, and communication.
Technical fluency is only one part of the role
Randy Deutsch said interpersonal intelligence was one of the most important and overlooked parts of the profile. Much of the learning happens through other people. The contributor has to know whom to ask, how to explain a change, and how to connect a tool to the problem the team is trying to solve.
Randy also described people who identify the real problem, connect ideas, communicate without demotivating the team, tell a useful story, and ask a strong question at the right time. The role is not defined by one software package.
The title may hide the capability
Randy Deutsch noted that firms use many names for these contributors, including design technologist and design technology specialist. He put the naming question plainly: “I don't think the name is really so important.” The characteristics in the same person mattered more than a standard title.
Randy also described people who did not consider themselves strong coders but showed deep curiosity, gathered public data, and worked persistently toward an answer. A narrow technical label can cause both leaders and employees to miss that contribution.
Career paths have not always matched the work
Randy Deutsch said these hybrid contributors did not always see themselves on the organization chart. Traditional paths in architecture and construction were clearer than the emerging routes through computational design or technology leadership.
Randy resisted calling that simple dissatisfaction. The concern was that the person carried more responsibility for defining a career path, while organizations outside architecture, engineering, and construction could recognize and recruit the same mix of technical and interpersonal skills.
Repeated work can reveal who is already connecting the team
Randy Deutsch pointed to recurring tasks as an entry point for computational thinking. When work repeats often enough to be understood, someone may notice the pattern and help the team test a more efficient method.
Repeated work offers a practical place to notice the capability. During a coordination, review, or model task the team already understands, watch who frames the problem clearly, experiments with the tool, and helps other people understand the change. Bring that full contribution into the role, support, and career conversation around that person.
The next technology leader may already be doing the work quietly. Leadership begins by recognizing the full contribution instead of seeing only the software skill.
