Optimization and increase of business efficiency are magic words for advanced managers. There are many recipes for this. The corporate portal, or also called the intranet, appears on the list. Electronic coordination, CRM with sales funnels, document flow - that just does not promise the business for a grand take-off after the introduction of corporate portals.
However, no one writes about the “intangible” price of the issue, about the risks, about how and why to create an intranet, and what difficulties it costs. They want two times, and the ship will sail. It is advisable to swim himself.
However, the implementation of the corporal portal is a multi-level, or rather wave-like, history. Many customers realize what kind of voyage they got into when they got on board the ship.
Me and my colleague, Pavel Meldazhis, head of the corporate implementation group, have seen and coordinated the implementation of corporate systems for several years from the inside. Completely different. Out of the box and completely custom, with budgets from a million to tens of millions. For all their differences, we came to an interesting conclusion: all intranet deployment scenarios can be reduced to two tactics. And each has its own waves and peaks.
We tell you how to stay on the waves of project implementation.
All-in-One Scenario
The history of the beginning of such projects is commonplace.
The client comes to the agency and says: “This is the budget that we are ready to spend on the portal. Let's implement a large-scale project. We need an electronic digital signature, automation of the filing of five types of applications, a 360 assessment system, an integration with 1C and our corporate system! If necessary, we are ready to expand the budget. ”
Even if the client came to the agency with more modest requests, there are three signs that the implementation of the corporate portal will follow the “All at once” model.
The Bermuda Triangle is formed by:
- Route. The project must sail its maximum route in a short time. Up to 80% of backlog is in the plan for development and implementation (!) In the coming year. Customers rush themselves and rush the agency.
- . . , . : - . . .
- . . — , . — «».
( ) , . , . .
, : , , .
« » ( ), .
. , . , .
№ 1.
. . .
. . , , .
, . - . . .
— , . ( ). « » ( , ) .
№ 2.
. , «». . .
. .
«» . — , .
, , , . , . , , , . , , . .
— , , . . : « . ? ?». .
№ 3.
, . .
.
.
- . , .
, . .
№ 4.
. , .
. , . .
, , . : .
, . .
, . — .
№ 5
. , . , .
, . , — , . . « , ». . — .
, , . . « , ». . , , . . . .
: , . , .
?
« » . , , .
, .
« »
« , !» — , , . . 80% .
«»
: «!». «, » .
— , . , , .
: , , , , , , .
, , , . , -, .
«»
« », , . . , . , - . .
. - , , (!) . .
, , , . . . , .
, « »
, « » — , . ( ), .
, . : , . « ». .
-, . , . «» . , «». .
: , , , . , . . . .
, , , , . , . , . , , — .
, , , . , .
«»
PR-, - . , , , . . , , . , . , 1000 .
. , - . , , . . , , , «», « - ».
«» , , . — , .
, . , — . , , , , . .
« »
, . . , .
« »:
- -. , . , , .
- . , , . , - . .
- , .
?
№ 1.
— . , . , .
, . - , . . , .
.
№ 2.
, . , , - .
— -, . -, . . — /.
№ 3.
. , . , . 360 , -.
— , «» . «, !». . , . , , … , .
, : , , , .
: , , , , , . , , , . , . « ».
?
. — , . , .
. , . . . , .
, , « », . , . , . - . . — , , — , .
, . , . , -- — , . .
-, . «» : - . . , : , .
: , . , . . - 9 , - 3 . , , .
, , . «-» . . 1 2, , « », .
, , .
, , , , .
, , . , ? , ?
— . , . , , . , . . : , . , . , , , . . .
— , , . , . , . . . —- , . , , .
, , . , . , , , , . . , .
, — . . . . .
A common practice can alleviate the loss - two employees are responsible for supporting the project: there is a project manager and an account manager. Their functions are a little different, but when one is lost, the second picks up the reins of government.
Berth
There is no ideal portal implementation model. Trite. Not new. But the truth. Often, one model after the first year of life flows into another.
The lesson that we all learned after going through both models of project implementation and which we advise you to remember is to form the correct client expectations. The contractor’s task is to explain what the chosen implementation model will entail when the portal is ready for use, when to wait, and when to push, why systematic support and financing are important.