You are here

Three reasons for templating project setup

There are many benefits to making your projects consistent and using a templated approach to setting them up.

Think about all the technology we use today, both in our personal life and our workplace.

Much of that technology is about managing information. From the humble photo library on your phone, to the platform used for managing project. For hundreds or even thousands of people.

When it comes to personal information, like that photo library on your phone, you can choose how to organize it.

For systems used by large numbers of people, you cannot leave that to individual preferences. Imagine, a photo library used by a few hundred people. All trying to group images into their own personal categories. Now imagine trying to find a specific photo from the millions in the library. Scary.

In Aconex, each project or program typically has its own space. That's where the team store the information. If you’re using Aconex across many projects, it’s tempting to configure each project differently. To suit the needs of each project. But there are benefits in making all your projects consistent.

Let's look at three reasons for using a templated approach.

1. Easier for teams to start working on new projects

When you manage information across many projects, it pays to be consistent. Aim for 80-90% consistency. The remaining 10-20% allows for specific requirements.

If you move between projects where each one is setup differently. It slows you down. You have to learn how each one is configured and how to find information. It creates cognitive overload and results in context switching – multi-tasking’s evil twin.

2. Quicker deployment

If you have a template, it makes it much easier to create and get started. Your agreed template allows us to get your project up and running quickly. Often it’s a quick call to double-check if there are any specific requirements and then you’re good to go.

3. Easier process management

Consistent project configurations make it easier to manage common processes. The reason? Each one will works the same way.

Teams will know what to expect and how to behave on every new project, based on their prior experience. This results in better quality data for your project too.

Consistency is the key to success in information management.

Was this article helpful?

Thanks. A ticket has been opened with the Support Central team.