Is it possible to improve the flow of projects and goals with Atlas?

Jean Horn

👋 Hello community!

I haven't yet implemented Atlas projects and goals. A question that comes up is: how do you prepare teams to use these new features while avoiding duplicate work between projects and epics?

One challenge I've faced is figuring out how to adapt a team's or project manager's workflow to Atlas, given that it offers a status-tracking view designed for management. But how do you demonstrate the benefits of using Atlas? How do you define goals and objectives with key results, and encourage the team to provide status updates?

I’m really not sure yet what the best approach is for introducing this and encouraging teams to adopt it.

Are you already using Atlas projects and goals with your team? How did you get started, and how do you handle the relationship with Jira tickets? Have you noticed any improvements in team performance or processes as a result?

👀 I’m curious to hear about your experiences!

Sean Perry

We adopted Projects and moved general status updates out of Jira into Projects. This enabled us to add people outside of our direct team to Projects as Followers to push status updates to them.
We worked hard to spread the word of the change to a wider audience to increase adoption, and within the team worked hard on making sure status updates were made only in Projects, and that they were written with a wider audience in mind.
Later we wrote a Rovo agent to gather Projects updates, Work Package statuses from Jira and project scope documentation from Confluence into a weekly project update email in a readable format as we don't allow Project access to internal parties.
Overall very happy so far. Need to look amaking changes to Project to capture more information, but that's planned for the next quarter.