Digital projects: 5 most common fails
These are the common pitfalls you should avoid on digital projects.
If you have ever entered a digital project with high hopes, great ambitions, and an aura of optimism-only to see these positive attributes crushed by the horrors of failures, delays, and red tape, you have come to the right place.
In order to never encounter these letdowns again, you should learn from the experiences of both yourself and other digital professionals. So, here they are-the five most common fails of digital projects.
1. Underestimating content production
This is the number one sin of most digital projects-especially those concerning the implementation of a new CMS or digital experience platform. There are indeed tons of tasks to do with the introduction of a new CMS, like planning the general architecture, site hierarchy, and templates, as well as the amount of sheer coding. But neither the vendor nor the implementation consultants are actually creating the content for you.
When you’re “creating a new website,” it’s fairly common to focus solely on the tech, glitter, and glam, and totally forget about content. Why, yes, the new design looks good, but what about the substance? What about conveying our values? What about describing what we actually do?
Don’t forget the content! It is what will actually populate that fancy tech and design of yours.
2. Not running an agile project
A project isn’t a project, so to speak. It isn’t like a game of chess where the board is firmly set and the rules are what they are. Instead, a project can be like an unpredictable, multi-headed beast you need a tight leash on, at least in some respects.
One common fail in this regard is the inability to prioritise tasks. Every feature and wish will not be finished by launch. This has been the inevitable nature of every large digital project in the history of humankind. Deal with it.
Classic waterfall processes are doomed to fail. In digital projects, several departments must collaborate, and it simply isn’t possible to dictate centrally that any given task shall be done then and then. A lot of factors play in, like the general workload of each department, when the next phase of the task is handed over from the previous stakeholder, etc.
Also, missing a definition of scope is a common mistake. This is why students in the school are taught to limit their project assignments. It’s better to write a specific essay about the fall of the Knights Templar in France, than writing a futile essay about the entire Middle Ages in general.
In other words: Don’t bite off more than you can chew. This is why you need to run an agile project -with modern organisational, collaboration, and working principles.
3. Not taking the reins
As an executive or a project leader, just putting your stamp of approval on a project delivered by external consultants and then minding your own business is a recipe for disaster. This is what happened in the Hertz and Accenture case, where the former is suing the latter for not delivering on a $32 million job to revamp the car rental firm’s online presence.
In any digital project, you need an internal dictator-a stakeholder that cares about the product. You need a Steve Jobs type, a passionate driver balancing technical savvy with project management know-how.
Imagine a film without a director: photographers, make-up artists, electricians, actors, and so on are great at performing their respective tasks, but they need direction and an overall guidance to make the end product work. Similarly you need an internal project owner to avoid projects missing scope, purpose, realistic deadlines, realistic budgets, and other terrible consequences.
4. Designing without purpose
As mentioned above, avoid the thoughtless “glitter and glam.” Your digital project has a purpose, whether it is implementing a CMS, integrating a new marketing automation system, optimising existing team processes, or whatever.
Especially for you: If you love smooth projects, you’ll love Enonic “
Design is not an end in itself-at least not in the world of business. Design should always support what you and your organisation are trying to achieve. Are you selling food online? Let your design enable the ease of transactions as well as making the foodstuffs more attractive. Are you delivering professional services? Let the design maintain your brand and tone of voice as a serious actor. And so on.
Function and purpose should always come first-design is secondary (albeit a necessary secondary factor).
5. Lacking automated tests
Let’s say you now have your digital project under control: content, an agile project, a passionate project owner, and a purposeful design are all in place. Are there still pitfalls to watch out for? Of course there is!
Here, at the end of the road, we have saved a severely important failure of digital projects: security. Forgetting the security aspect among all the other features is sadly a common mistake, and in order to prevent failures to happen in the first place you need to implement automated tests.
Setting up automated tests must be done in collaboration with your IT and quality assurance departments. Remember to focus on testing the most important parts of your digital project, e.g. a secure order form for a business, or a functional user account on a social network.
While there certainly are more fails and pitfalls to digital projects than these, the included list is the most crucial failures to avoid. Take action and you will deliver excellence.
Originally published at https://enonic.com on October 30, 2019.