Solution Vs Technical Architect. What's the difference?
Do you know the difference?
It’s ok. Most people don’t.
And that difference, especially when leveraged on a project, can lead to incredible results.
In this episode, I’m going to break down the responsibilities of each and why they are both important to your project delivery team.
Over the past decade, I've helped dozens of companies better understand Adobe technology and project delivery. Along the way I've had the opportunity to see a lot of what works and a lot of what doesn't. My goal is simply to share with YOU what I've learned. And I hope that gives you back a little sanity in your day.
💡 What do you think? Share your thoughts in the comments and let's have a conversation about it.
________________________________________________________________________________________________
Transcript:
Do you know the difference between a solution and technical architect? Knowing this is a key to your success.
Okay, so let's dig in. The difference between a solution architect and a technical architect can best be understood through an example. So let's say a client is looking to do a larger digital transformation. It could be replatforming a legacy system or implementing a new system altogether.
That company would typically hire professional services company. And in turn that professional services company will assign a delivery team.
As part of that delivery team, most often you'll have a technical architect because after all the initiative itself is technically heavy with requirements.
And just like it's heavy with requirements, technically there's also a lot of requirements from the business side.
Both the technical and business requirements need to look across people, process and product. Understand the current state. Look to the future state. And to be able to define a path to get there.
Now the solution architect is going to look at what to build. What to build across people, process and product, taking into account existing systems, people, roles, maturity level and goals.
The technical architect is going to look at how to build it. How to build it across people, process and product. Taking into account legacy technology, data, APIs, security and scalability.
Now you can see why having both a solution architect and a technical architect as part of the same delivery team dramatically increases the overall success of the project and it being delivered.
So, what do you think. Leave a comment and let's talk about it