# data[].attributes.headline
Working with stakeholders as a team on a shared understanding of the scope, what's most important to work on and why (not being afraid to question the initial ask) 

# data[].attributes.subject
Working with stakeholders as a team on a shared understanding of the scope, what's most important to work on and why (not being afraid to question the initial ask) 

# data[].attributes.body
I think having some shared ownership on what is being worked on is pretty important

# data[].attributes.headline
Time for discovery at the beginnings of work

# data[].attributes.subject
Time for discovery at the beginnings of work

# data[].attributes.body
Investigate what the stakeholders want, why, what the user needs are, review analytics, etc.

# data[].attributes.body
Short scrums every day work well to check in and understand dependencies

# data[].attributes.body
Team time/pairing works well to keep everyone aware of work being done/get feedback/learn new things

# data[].attributes.headline
Make time for user research in our projects

# data[].attributes.subject
Make time for user research in our projects

# data[].attributes.body
I like that we find ways to get our work out in front of users, consistently, sometimes unconventionally

# data[].attributes.body
I like having the project be the focus and knowing that I can contribute in different ways— QA'ing, helping with content audit— to bring the project to realization. Makes me feel flexible and holistic in my work.

# data[].attributes.body
It's nice to have a no-meeting day/have time to focus on work

# data[].attributes.body
I like working closely with people from other disciplines: we all bring different perspectives that are valuable and valued

# data[].attributes.body
The team has a pretty high degree of independence and flexibility in how much work they take on and when it happens; it is not dictated to us by the stakeholder. I think this helps everyone take ownership over their work and remain invested in the success of the project.

# data[].attributes.headline
Having a key stakeholder integrated in the team's meetings, cadence, etc

# data[].attributes.subject
Having a key stakeholder integrated in the team's meetings, cadence, etc

# data[].attributes.body
Gets away from us/them attitudes that might come up otherwise

# data[].attributes.body
We're pretty good at knowing who should be doing what and when, also respectful of each others' role boundaries, also free to comment/give feedback on each others' work

# data[].attributes.body
Sometimes it can be hard if my tasks are dependent on other tasks. Hard to know best ways to contribute without being redundant with other people's work. Helpful to build "side work" into sprint.

# data[].attributes.headline
Making time for relevant "pet" projects 

# data[].attributes.subject
Making time for relevant "pet" projects 

# data[].attributes.body
We highly value doing this on our team and make time for it: making new/improvements to wagtail patterns, creating a whole new photography style, etc

# data[].attributes.body
Aside from daily design time being good for working, it's nice to simply have face time with a small group and get to know people since we work remotely and don't have an office culture.

# data[].attributes.body
We try not to overload ourselves, we aren't driven by external deadlines. We are realistic about what's possible in a given two-week period.

# data[].attributes.body
Focus on MVPs

# data[].attributes.body
in addition to all these other things, I also feel like we are lucky in that we have really nice and conscientious people on this team - and we haven't been subject to the whack a mole distractions of doing lots of small projects that can come in any time. i don't know where these random observations fit

# data[].attributes.body
Can be difficult to know what other teams are doing, especially related to communal work (like design manual, CF)

# data[].attributes.body
Github works well for breaking down tasks and documenting

# data[].attributes.body
Can be tough to get external developer eyes on our work as a project team

# data[].attributes.headline
Willing/able to make time to learn across disciplines from each other

# data[].attributes.subject
Willing/able to make time to learn across disciplines from each other

# data[].attributes.body
all these things work well as a small project group in particular. having an established time on the calendar, space to talk about all things from personal to work process related.

# data[].attributes.body
working on the same thing may be important (as opposed to design ops or platform, with no collaboration on one big thing). Shared responsibility for seemingly small projects — tying them to the larger meaning

# data[].attributes.body
Tie work back to goals, seeing small work as all part of bigger streams of work, focusing on that, opens up room for strategic thinking, etc

# data[].attributes.body
<--- team time

# data[].attributes.headline
Reflection time every 4 months in person

# data[].attributes.subject
Reflection time every 4 months in person

# data[].attributes.body
Talk values, talk process, talk goals

# data[].attributes.body
Underlying motto of "continue improvement"

# data[].attributes.body
"I don't want to let my team down"

# data[].attributes.headline
Real clear direction, what is important, why we're doing this

# data[].attributes.subject
Real clear direction, what is important, why we're doing this

# data[].attributes.body
Again, larger meaning

# data[].attributes.body
- listening... what are we missing, learning from stakeholder
- Product owner is one role of whole just as UX, FEWD, GD, PM are
- integrating stakeholders into team, equals, welcome to family

# data[].attributes.body
Everyone has a good attitude

# data[].attributes.body
We can control within the bubble