Client Interactions
Project Management
Section titled “Project Management”The Project Management meetings with the client are extremely important for relationship building, transparency, decision making, alignment, issue management and client satisfaction. These should happen once a week (or at least once every 2 weeks). These meetings should include all of the engineers that are working on the project and each engineer should give an update on the tasks that are being worked. These meetings help to show the client that we are focused on and invested in their project’s success.
During this meeting it is important to listen for concerns from the client, concerns from the engineers and scope changes. Address the concerns quickly and verbally, restating the concerns so that everyone is on the same page. If it is not immediately remedied, take it offline while working on a solution, but let the client or engineer know when you’ll get back to them. For scope changes, ask for a detailed explanation that outlines the changes requested. Based on the contract, it may require a change-order to implement the scope changes.
If tasks are being tracked on a Jira board, the Jira board should be displayed and used to help picture the status of the projects and keep the meeting on-track.
Account Management
Section titled “Account Management”Note: This section was truncated in the original source. The Account Management role generally falls under Sales. When working with the client in an account management capacity, the primary purpose is to understand the client’s goals, direction and satisfaction with Lab651, and to identify ways to improve or expand the engagement.
Related
Section titled “Related”- Client Cadence — setting transparent client meeting rhythms
- Client Buy-In — earning client alignment with Agile