In the first of our new Built to Lead series, we speak to Sidra Ansari.
Sidra joined UP3 just over two years ago as a technical consultant. Earlier this year, she was promoted to senior technical consultant, and she is now on secondment as a technical architect on one of our largest and most complex customer accounts.
Here, she talks about learning to let go of the ‘doing’, working directly with ServiceNow’s product teams, and why no question is ever a stupid one.
Technical enough after all
I studied mechanical engineering at university, then did a master’s in computer science. That gave me a year of coding and programming, but not much more. Coming out of university I worried I wouldn’t be technical enough for a software role. I didn’t even know technical consultancy existed.
So, when I was offered a role as a ServiceNow technical consultant, it was a revelation. The technical knowledge I needed was in line with what I had covered at university. You don’t need to know the ins and outs of every line of code. In fact, I discovered quickly the role is just as much about people as technology.
“You get the best of both worlds - the problem solving, and the people.”
It’s a role of two halves. The consultancy half is talking to customers, running workshops and understanding what they want to implement or fix. The technical half is turning those requirements into a solution and building it. You demo what you’ve built, take feedback and adapt it. This combination suited me perfectly because I love talking to people as much as I love problem solving.
Stepping into technical architecture
I was promoted to senior technical consultant in April 2026 and a few months later, the project needed an architect on it. I’d been on the project long enough to know it well and because I’d worked across so many areas, I already had a broad view of the customer’s business. The opportunity aligned well with where my skills lie.
Architecture takes a different mindset. As a technical consultant, you can think quite linearly - here’s the requirement, here’s what I need to build. As an architect, you need to ask how that requirement fits with everything the customer already has, and everything they want to achieve in the future.
“Like an architect designing a building, you need the bigger picture.”
That means asking who, where, how and why, not just what. If a customer wants a new integration, how we build it is one conversation. Whether they should, and how it fits with the rest of their system is another. That’s where the role of an architect adds real value to our customers.
Learning to let go
Personally, the biggest shift in this secondment has been letting go. I like to be hands on and in control. If something needs doing, my instinct is to do it myself.
As an architect, my focus has moved from building individual pieces to shaping the whole solution: making the design decisions, making sure everything fits together and spotting risks early. That means handing the build to a really capable team, including work I was doing myself only weeks ago. Breaking the habit of jumping in has been a real learning curve, but it's where I can add the most value
Working with ServiceNow at the source
One of my proudest moments in the technical architect role so far has been working directly with ServiceNow.
Sometimes a customer needs an enhancement that really belongs in the core product, so we go back to the source and work with the ServiceNow team.
As a technical consultant, I’d never have been involved in that. As an architect, I’ve spoken to ServiceNow’s product teams about how their product works behind the scenes, and how an enhancement could be built in for customers in the future.
You implement the product every day, but you rarely see how it’s built. That’s been fascinating for me.
What I’ve learned along the way
My advice to anyone following a similar path is simple - ask the question.
Every question you ask opens a discussion or teaches you something. And if you don’t ask, people may assume you’re happy staying in your own bubble.
“When I joined UP3, I didn't see myself on a technical architecture secondment within two years”.
I’ve also learned how invested I get in work I find interesting and where I can see the impact of what we are doing.
I know I do my best work when I care about what I’m doing. And understanding how a project I am working on impacts the people at the other end of the project – employees or end customers – makes it very easy to care.
Quickfire Q&A
What do you love most about working at UP3?
I know everyone says it, but it's the people. I wouldn't enjoy coming to work without this team. Even when things are pressured, everyone stays calm, supports each other and still has fun. A few weeks ago, I had a 3am customer go-live, and a colleague offered to join me so I wasn't doing it alone. That's the UP3 spirit.
What does Built to Lead mean to you?
When I joined UP3, I didn’t see myself on an architecture secondment within two years. But I’ve been given a complex project that’s challenged me, real responsibility and the support to grow into it. For me, Built to Lead is about being given those opportunities, being supported to thrive in them and being trusted to step up when the moment comes.
What excites you most about UP3’s future?
We’re always growing. There are always new customers coming on board and new challenges to get stuck into.
Inspired by Sidra’s journey? We’re always looking for talented people to join our team. Explore our current vacancies at https://up3.co.uk/about/servicenow-careers-with-up...
