Important project knowledge often ends up scattered across emails, meetings, chat messages, and personal notes. As projects progress, it becomes increasingly difficult to remember why certain decisions were made, how a visualization was created, or what assumptions guided the analysis.

Instead of allowing that information to live in disconnected conversations, document it directly within your project files whenever possible. Useful comments may include information such as:

• Workflow decisions
• Processing steps
• Assumptions
• Customizations
• Interpretation notes
• Revision requests

Capturing this context alongside the work itself preserves valuable project knowledge, improves transparency, reduces repetitive questions, and helps future reviewers understand the reasoning behind the final deliverable much more quickly.

For example, with tools like Surfer and Grapher, users can leave in-product comments directly on their visualizations to explain why a particular gridding method, contour interval, graph scale, customization, or formatting decision was selected (see images below). Rather than wondering how a map or graph was created months later, teammates can immediately understand the reasoning behind it.

Even highly collaborative teams can become inefficient when responsibilities and review processes aren’t clearly defined. But team members should never have to guess who owns a task, who reviews deliverables, or when feedback is expected.

To create consistency, establish clear expectations around the following:

• Project ownership
• Technical reviewers
• Final approvers
• Stakeholder communication responsibilities

Communication should also be specific, actionable, documented, and easy to follow so everyone understands what needs to happen next. 

In practice, this could look like having a predefined review process for a groundwater mapping project where technical review occurs first, followed by project management review, before the maps and models are released to stakeholders. With this clear review process, there’s less confusion, clearer expectations, and fewer delays.

One of the fastest ways for collaboration to break down is when important project information is only available to a few people. Instead of allowing key insight to remain among select team members, create shared locations where everyone can easily access information.

Some of the most important details that should be easy to access include the following:

• Project updates
• Assumptions
• Key decisions
• Action items
• Revisions
• Final outputs

This information can be stored within project files, shared folders, meeting notes, or other centralized resources that team members can access. A consulting team, for instance, may maintain a shared project workspace where the latest maps, graphs, reports, comments, revisions, and project updates are always available to everyone involved.

Not every part of collaboration requires technical expertise. Many administrative tasks consume valuable time that could be better spent analyzing data, enhancing visuals, or reviewing deliverables. To help team members focus more on critical tasks, incorporating AI into workflows is helpful. 

AI can streamline routine activities such as:

• Meeting summaries
• Action-item extraction
• Organizing project notes
• Summarizing discussions
• Drafting follow-up communications
• Formatting data for maps, graphs, and models

Here’s an example to put this into perspective: after a project meeting, AI tools can generate a summary of key decisions, action items, and next steps, giving every team member a clear record of what was discussed. 

Strong collaboration depends on open communication, and that begins with making questions a normal part of the project workflow.

Throughout the project, encourage team members to do the following:

• Ask questions
• Challenge assumptions
• Seek clarification
• Offer alternative perspectives

Creating opportunities for these conversations helps identify issues earlier, reduces unnecessary assumptions, and leads to stronger technical discussions.

For example, a weekly project meeting might reserve time specifically for team members to raise questions or concerns before deliverables are finalized, giving everyone an opportunity to resolve uncertainties before they become larger problems. When people feel comfortable asking questions, collaboration becomes more effective, productive, and ultimately more successful.