The project tool began drafting status

On 3 October, Asana announced several AI functions. Smart fields, editing, and summaries started rolling out that day. Smart status, intended to identify risks, open questions, and blockers from work data, was scheduled for winter 2023. Other planning, capacity, and workflow functions lay further ahead. The company’s release therefore distinguished available capabilities from its roadmap, even though its benefit claims were broad.

For a project manager, an automatic summary is useful when it reduces searching through tasks and comments. Status must still relate to an agreed period, milestone, and accountable person. A model can find many open tasks without knowing which one threatens delivery. A control point should consequently compare the summary with the project plan and record which risks were missed or assigned the wrong priority.

Documentation connects with execution

On 16 October, Atlassian showed how Jira and Confluence could work together. Project pages collected requirements, sprint goals, and design descriptions. Release notes could be created from Jira and updated when the release changed. At the end of a sprint, a team could create a retrospective page linked to its burndown chart.

This is more than document sharing. The connection makes it possible to follow a decision from its background and requirement through task, delivery, and later learning. The team still has to decide which system owns each field. If end date, scope, or accountability is updated in several places without an authoritative source, the amount of visible information grows while governance becomes less reliable.

Collaboration should be measured through real handovers: how often a decision lacks its rationale, how many release notes need manual correction, and whether retrospective actions become new tasks. Documentation then becomes part of the project control loop rather than an archive beside the work.

Analytics development becomes a team delivery

The October Power BI update emphasised shared ways of working. Microsoft described viewing and editing Power BI files in OneDrive and SharePoint, a model explorer in Desktop, and improvements to deployment pipelines. These functions affect both report authors and users who need to understand which version they are viewing.

For analytics governance, the model explorer matters because measures, relationships, and other model elements are easier to find together. Shared files can shorten the path from draft to feedback, but they do not replace named owners, quality review, or a separation between development and approved reporting. A delivery pipeline should show who approved a change, which data basis was tested, and what happens if a report needs to be rolled back.

A concrete control point can be a change log connecting every new measure or visual with a project need. Before the next deployment stage, another person checks the definition, access rules, and a known test result. This makes the review visible and reduces the risk that a technically successful publication is mistaken for subject-matter approval.

The same requirement applies to AI and analytics

Asana, Atlassian, and Microsoft covered different product areas, but the management need is the same: status and analytics must be traceable to underlying work. AI can draft a summary, and a reporting tool can make a model easier to share. A decision becomes reviewable only when the team can find the task, definition, data version, and approver. A bounded pilot should therefore measure both time saved and the proportion of status points or report changes corrected before use.

When error types recur, the log provides concrete input for training, clearer data definitions, and workflow adjustments.

Sources

Asana, 3 October 2023

Atlassian, 16 October 2023

Microsoft Power BI, 11 October 2023

Join the discussion

Where do misunderstandings most often occur between planning and delivery in your team? Share an example from an assignment.