From Design to Data: Why Thinking Differently Matters More Than Technical Skills

Yosh Lotfi didn’t take the usual route into data and technology. He started out in industrial design, but even then he wasn’t just focused on what he was creating. He was thinking about how everything fit together.

How ideas turn into products.
How products turn into businesses.
And how none of it really works unless the system around it works too.

That mindset still shapes the way he works today.

Now a Cloud Solution Architect at HSO, Yosh operates in the space between business and technology. He helps organisations not just solve problems, but step back and rethink whether they are solving the right ones in the first place.

“Design teaches you how to think. Technology just gives you the tools to apply it.”

Starting in design, but thinking beyond it

“I studied industrial design, then design management,” Yosh says. “But I was never just interested in the end product.”

For him, the interesting part was always what sat behind it.

“When you design something, it doesn’t really exist in isolation. It only becomes real when it works within a business. And a business only works when all the moving parts connect.”

That is where his thinking shifted early on. Away from outputs and towards systems.

Learning how to think, not just what to do

Design gave Yosh something that is easy to underestimate. A way of thinking.

“People often see design as purely creative,” he says. “But it is actually quite structured. It teaches you how to break problems down, look at them from different angles, and challenge what you are being told.”

That foundation ended up mattering more than any specific tool or technology he would go on to learn.

Finding his way into data

Yosh didn’t move into data because he planned to. It happened more organically.

“I remember one of my early interviews,” he says. “I answered the questions, but then I started talking about bigger patterns. Where things were heading and how different pieces connected.”

At the time, data and AI were not the buzzwords they are now.

“But that is what made them stop and really listen.”

It wasn’t his technical depth that stood out. It was the way he approached the problem.

Where design and engineering meet

As Yosh moved into data engineering and later pre-sales, he started to notice a clear difference in how problems get approached.

“Engineering is about precision. Doing things right,” he explains. “Design is more about exploration. Asking if you are doing the right thing in the first place.”

Both are essential. But they do not always get equal attention.

“A lot of organisations are very strong on execution,” he says. “But there is not always the space to step back and rethink the approach.”

That is where he naturally fits. Not replacing engineering, but complementing it.

Making complex things make sense

In his role today, Yosh spends a lot of time translating complexity into something people can actually use.

Because the challenge is rarely just technical.

“One client came to us convinced they needed a new data platform,” he says. “But when we stepped back, the issue wasn’t the technology. It was how their teams were using the data they already had. We changed the approach before writing a single line of code.”

For him, simplifying does not mean oversimplifying.

“It is about structure. If something is clear, it is because it has been thought through properly.”

And that clarity is what helps organisations move forward with confidence.

Why it works at HSO

That way of thinking is something HSO actively makes space for, particularly as it expands its capabilities in cloud and AI.

“You are not just here to deliver,” Yosh says. “You are expected to bring your perspective. To challenge things, even when that means slowing down before jumping into a solution.”

That creates a different kind of environment.

One where value is not just measured by output, but by how you think, how you collaborate, and how you shape the direction of a problem.

“Innovation is not always about new technology,” he adds. “Sometimes it is about looking at the same problem differently and being given the space to do that.”

A different way to define expertise

Looking back, Yosh does not really see his career as a shift from design to data.

It is more consistent than that.

There were points where the move was not obvious. Stepping away from a traditional design path into something less defined carried some uncertainty. But the underlying approach never changed.

The tools have evolved. The context has changed. But the way he approaches problems has stayed the same.

“The technology will always move,” he says. “But the thinking behind it, that is what actually makes the difference.”