Stakeholder Engagement

3 Ways to build stakeholder engagement

Apathy is the enemy. Getting things done is wholly predicated on stakeholder engagement.

Increasing project engagement is a challenge across all industries, particularly verticals that are highly specialized, which make project data difficult to share across multiple teams.

However, with a few key tools and better communication, you can build stronger stakeholder engagement, align project vision, and accelerate decision making. Review the three steps below to improve engagement across building designers, architects, engineers, manufacturers, fabricators, risk assessors, project owners, and more:

  1. Provide all team members access to relevant project data.
  2. Enable contributors to provide feedback instantly, anywhere.
  3. Encourage communication across teams.

Provide seamless access to project data

The first step to increasing stakeholder engagement is simply to enable all team members access to project data that they need access to.

Design files are complex and sharing them can be complicated. Tools exist to enable sending design files, but it’s infinitely better to use a tool that was built for sharing and collaboration. Utilize a tool that enables users to access and view these files from a central location from any device. It’s crucial to remove barriers to entry to increase stakeholder engagement.

Enable instant feedback, anywhere

Stakeholder engagement is quantifiable; it can be measured in telephone conversations, clicks, views, notes, and feedback. Providing feedback can be arduous when the only possible routes are email, telephone conversations, and change request documents. A full cycle of feedback, changes, and revisions, (rinse repeat) can take weeks, even months to complete. Enabling team members, contributors, and project owners to provide feedback directly within a file through markups, comments, and live review sessions, removes obstacles to gaining consensus among all stakeholders.

“There are challenges when collaborating on international projects: time zone plays a role in availability and there are different standards in various locales. It’s tremendously beneficial to have immediate feedback that is not in an email.”

Luis Cetrangolo, BIM Manager at Tsoi/Kobus & Associates

When all project feedback is collected in one place, on files that are in a central location that can be accessed from virtually any device, then stakeholder engagement increases and key decisions can be made more quickly.

Reduce the barrier to entry to increase stakeholder engagement.

Encourage communication across teams

Communication is paramount when working with a team. Everyone has a role to play, feedback to provide, and discussions to have with other contributors. It’s best when communication happens on one platform, comments made on the same files, and the same wiki pages are used for reference.

Communication can be superfluous if transparency is lacking, but when the whole team is on the same page (or the same platform), processes are streamlined:

“…collaboration tools help drive efficiency and streamline how teams can be managed, making work between remote teams, clients, architects in the office, and construction workers on the ground much easier.  In this way, the set-up, format, and workflows that the industry uses are changing.”

Allan Partridge, Principal, Next Architecture Inc.

Remove barriers instead of forcing new processes on deaf ears. Eliminate steps like email, printing, and telephone calls to increase stakeholder engagement.

A360 is enabling teams to create more project transparency, make decisions faster, and invite their clients into the design process. Learn more about A360 to start building stakeholder engagement.

Colin Piper

Colin Piper is a Senior Marketing Manager for Project Delivery and ReCap.

More Posts

1 reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>