Architecture - the missing link between sales and delivery?
Having worked in a number of consultancy organisations I have plenty of experience of projects (or people) being mis-sold by sale teams and the delivery side of the organisation having to pick up the pieces. Often this is in the form of working people into the ground to deliver on a misguided promise, and sometimes it is in the form of having to replace good people when they get disillusioned.
Quite often this situation arises through the desire of a sales team to "meet targets" irrespective of whether an opportunity is strategic or in fact achievable.
It is clear to me that this is behaviour that needs to be controlled in someway in order to prevent organisations from churning through people and having to continually employ to stay at the same size, and from lacking any sort of technical direction.
Often there is a process of career guidance in place in an organisation that is supposed to help ensure that people get the right opportunities to develop their career in line with their aspirations. Whilst being a noble cause, this often fails to achieve its goals as the guides have no say in the opportunities available.
So how do we ensure that the sales team is selling things that are in line with the aspirations of the staff, the technical direction of the company, and that are deliverable?
It is quite common for organisations to carry out in-depth bid reviews before a bid is actually submitted to a client, but to my mind this is too late. There needs to be continuous, upfront technical involvement in the sales process. This could involve an individual architect taking responsibility for the technical direction of an account, or a group of architects taking responsibility for all accounts. This group of people would also help to enforce the technical direction of the company, and can facilitate technical knowledge sharing across accounts to enable work to be more effective. All opportunities would be passed through this person (or group of people) before a commitment to bid for/take on work is made. They would have the power to veto any individual piece of work, so long as they can provide adequate justification for doing so.
There are several significant barriers in most organisations to the adoption of an approach such as this. Chargeability is perhaps the most significant barrier - there is such pressure to keep people utilised 100% of their time on paying work that this sort of thing is rarely sponsored at the right level. This lack of sponsorship leads to the issue of empowerment. People need to be given a lot of power/influence in order to be able to effectively do this role - it is far too easy for the sales team to ride roughshod over technical people, or simply ignore them entirely. I have had first hand knowledge of this on several occasions.
Is anyone out there lucky enough to be involved in the sales process in this way? If so I would love to hear how it works in practice, and whether it has made a difference to the organisation as a whole. Or is there a more fundamental question here with regards to the effective size of a consultancy organisation, although that subject is perhaps dealt with in another post.
Re: Architecture - the missing link between sales and delivery?
In our company architects are part of the bid team. In bigger bid teams you can say that the solution architect represents the sales organisation, while the infrastructure architect represents the delivery organization.
Furthermore most product/solutions are being developed/maintained by a team with members from the sales, the project and the delivery organisation. So everybody knows exactly what they can/must sell, implement and manage.
Regards, Peter
Re: Architecture - the missing link between sales and delivery?
It is often suggested that a member of the sales team joins the support team (or development team) for a week of the warranty period (or delivery). Cause meeting effect can be quite interesting - see the end of Timecop for what might happen!
I do feel sorry for sales teams in this regard - they are treading a fine line between unrealistic and undesirable. An architect should be involved as early as possible - not only to keep things achievable, but also to represent the sales team's requirement - that of remaining competitive.
Re: Architecture - the missing link between sales and delivery?
The process appeared to work well, resulting in a bid that had a far sounder foundation from a technology point of view.
Conversely, I have also been involved in projects where a customer has been sold a technology as the panacea for all of their problems, leaving the project team to hack together some really half-baked solution around a completely inappropriate technology.
Re: Architecture - the missing link between sales and delivery?
While sales is a channel for customer requests, sales can also be a commitment source that causes scope problems, and if sales has too much visability into the next release, they will sell it, which would be fine if the schedule is met, and not fine when the schedule isn't.
In one company, sales was so busy selling the next release that they didn't sell the current one. Cash flow problems insued. And, the next release kept on slipping.
Somebody has to be the gate between sales an dev. I'm not certain it is within the scope of the architect. Of course, architects want to expand their jobs, so ...
Re: Architecture - the missing link between sales and delivery?
Management formed board of architects and designers together with presales team who will be involved in any major delivery with presales team, didn't work! Most presales guys assumed it's achievable but ground competencies and mismanagement at every level crashed it badly...
Then? well, then everyone left....











