One Project, Many Lists: Connecting People, Assets and Follow-Up
Illustration created for Osteam
A customer project has an owner in a project board, hours in a timesheet, equipment in an asset list, and follow-up actions in meeting notes. Each record may be accurate. The problem appears when someone asks a simple question: who owns the next step, and is the team ready to do it?
Choose the decision before the dashboard
A broad company dashboard is tempting, but a useful first step is narrower. Choose a decision people already make every week: whether a project can start, whether a deliverable is at risk, or whether a meeting action has actually been closed. List the facts needed for that decision and where each one lives today.
- Project: customer, scope, due date and accountable owner.
- People: availability, activity and responsibility for the next task.
- Assets: required equipment, assignment and current status.
- Follow-up: the action, owner, due date and reviewed outcome.
Give records a shared reference
Connecting work does not mean merging every database on day one. Start by agreeing on a stable project reference and a small set of fields that each team recognises. An asset assignment can point to that project; a meeting action can point to the same owner and work item. The reference reduces repeated entry and makes the trail easier to inspect.
The harder part is ownership. Decide which system is authoritative for each field, who may change it, and what should happen when two values disagree. Without that decision, a new workspace can become one more place to update.
A useful first measure
Count how often the team asks for a status update that should already be recorded. Then track how long it takes to answer before and after connecting one project workflow.
Add modules where the link matters
A modular workspace can start with projects and people, then add assets or meeting follow-up when those links are needed. The value comes from related records remaining together as work changes. A report should reflect the underlying activity, not depend on someone rebuilding it from emails at the end of the week.
This is the idea behind XAAX: a connected company workspace for projects, people, assets and daily workflows. Its meetings capability is in beta, so the right pilot should be based on the modules and steps your team can use now.
Keep the first rollout small
Pick one team and one project type. Map the current handoffs, connect only the records needed for one recurring decision, and review the result with the people doing the work. If the link removes chasing and duplicate entry, add the next module. If it does not, fix the workflow before widening the rollout.