# data[].attributes.body
develop a pm approach -- purpose, tools used, what each tool is used for, problems we use this approach to solve for, etc.

# data[].attributes.body
no uniform single practice for all when it comes to referencing monday (e.g. daily? weekly? all boards? A vs R should be looking for what exactly?)

# data[].attributes.body
inconsistent docs and monday integration / norms

# data[].attributes.body
we can't see clients and internal work side by side, never have a clear picture of everything we are doing

# data[].attributes.body
doc mgmt, version control, and google docs in general could use a refresh on norms -- using an old structure but it needs an update now that we've added fathom into the mix

# data[].attributes.body
I really think that we just like google docs and spreadsheets. I wonder how likely we are to adapt any tool fully

# data[].attributes.body
be more consistent with prep calls, not just focused on the work but also roles on the client meeting to support growth and development of team members

# data[].attributes.body
No single place to go to for project reference where everything can be found. Multiple places and inconsistent updating.

# data[].attributes.body
the work to get on another tool, knowing they all rely on consistent adoption, is a concern for me

# data[].attributes.body
clients in particular are well documented and detailed, maybe a bit more than necessary, but much better than where we used to be which was having everything in individual brains on the team

# data[].attributes.body
We have to be consistent in our adaptation of any tool we choose

# data[].attributes.body
no consistent 'language' of use (naming convention, consistent statuses/colors, expectations for use) across different parts of monday.com

# data[].attributes.body
Reminders to update channels and platform regularly

# data[].attributes.body
changing our client management practices and choosing a new PM tool gives us a natural reset as a team and opp to better adopt and utilize a new path fwd

# data[].attributes.body
retroactive use of tools and platforms

# data[].attributes.body
Consistent and regular referencing of the platform in team calls

# data[].attributes.body
Dedicated slack channels for clients and internals, helpful for keeping things in one place and to reference as record

# data[].attributes.body
stronger doc integration so we aren't working in a platform side by side with gdocs, click up is a great example of this

# data[].attributes.body
Monday client view has the potential to solve some of our issues

# data[].attributes.body
inconsistent adoption and lack of accountability to use the tools

# data[].attributes.body
Simplify and streamline, less redundancies and simpler practices with clients ie. pull takeaways and decisions from Fathom

# data[].attributes.body
I haven't seen another project management tool that feels like it would solve our problems - it would just give us a blank slate

# data[].attributes.body
Consistent doc practices across clients

# data[].attributes.body
Automations with slack are great

# data[].attributes.body
Monday's political stance

# data[].attributes.body
There are so many individual tasks on Monday that it just feels like a bunch of stuff thrown on the board

# data[].attributes.body
Required to look in many different places to understand what is happening with a client or project, monday search function is particularly cumbersome

# data[].attributes.body
we can change the way we use our tools/Monday, and this timing feels good because we're changing the way we set up projects

# data[].attributes.body
Monday orients toward tasks but not full project visibility

# data[].attributes.body
We use both docs and Monday, and it isn't necessarily clear what should be used when

# data[].attributes.headline
multiple mediums capturing the same/different work streams

# data[].attributes.subject
multiple mediums capturing the same/different work streams

# data[].attributes.body
we don't have a way to see all project moving at once to understand how timelines intersect/ capacity impacts

# data[].attributes.body
unclear timeline with clients leads to inconsistent client management and scope execution

# data[].attributes.body
Monday automations are really helpful for knowing what needs to be reviewed and when

# data[].attributes.body
inconsistent adoption and over-indexing towards task management over project management

# data[].attributes.body
Redundancy across tools and docs, including duplication of material for client and internal use

# data[].attributes.body
Monday automations and approvals are smooth

# data[].attributes.body
We document a lot through notes docs and Monday

# data[].attributes.body
adoption/ consistent use of PM docs and tools

# data[].attributes.body
Should we go the path of choosing another project management platform or system, what might get in the way of us executing successfully? What is a current barrier to successful client project management across all client teams, if anything?

# data[].attributes.body
Where could we be more consistent in our project management practices? What feels duplicative or unnecessary? Where are there inefficiencies? What are our greatest areas of need when it comes to project management?

# data[].attributes.body
What isn’t going well? What practices feel inconsistent across teams? What practices are contributing to ineffective project management?

# data[].attributes.body
What are we doing well? What practices feel like they are consistent across client teams (think management, docs & platform usage)? What practices are helping us manage projects effectively?