How many Architects does it take to draw a picture of your business?

You have an extensive Architecture practice with a hierarchy of roles. Business, Enterprise, Solution, Data, Functional, Integration, Cloud, and an ever-expanding group of titles. Did you ever wonder what all those people are doing?

Many businesses have been trying to get control of the increasing complexity of their enterprises and Architecture is seen as a way of keeping an eye on things. The challenge is the roles seem to be proliferating with new specialisms all the time. How many Architects does it take to draw a picture of your business?

Of course it’s challenging

Part of the challenge lies with recruiters who have algorithms to help them “filter” out unsuitable candidates. It can be so easy to apply for a role, just one click on some web sites. This means candidates often do not read the job description. They see the title and fire off their generic CV. That means there may be over 100 applicants to each role. Rather than sifting those manually to select the best candidate, the requirements are put on a system and only those CV which score highly end up on the recruiter’s desk. That though means categorisation. The problem with that is you only pass if you have done exactly that thing before. This leads to experienced candidates with diverse skill sets being rejected. Someone with only 2 years’ experience may get through where someone with 15 may not.

Another part of the challenge is the client. They may well demand very specific experience as they need confidence that recruit will “hit the ground running”. Only someone who has done this thing, with this technology, in this environment (preferably for a direct competitor) will do. That may be understandable although limits the pool of possible candidates and talent.

Clients also have another big challenge as they mostly only recruit one way. Many clients will recruit a temporary resource like a permanent one. They speak of culture fit, make many checks, interviews, and tests for someone they may only need for 3 months! Or sometimes for a specific piece of work which a good candidate could deliver in 6 weeks. Those six-week contracts are rare though. Mostly it’s 3, 6 or even 12 months because the candidate must work exclusively for this client. One client at a time. The client even insists the candidate work from their office 5 days per week and sometimes insist on a start and end time. This is not an interim, this is a permanent employee.

There is another way

There is now a better way. What if you could access high quality talent for as little as 1 day or as much as you want? What if you could just say what you need and someone with those skills turns up the next day.
That’s what Architecture as a Service from Café does.

 

Adam is an expert in applying system thinking to resolve many complex and difficult business problems for some of the world’s leading companies.