# data[].attributes.body
Current State:

Mismatch between volunteer pool and needs of school sites

Timeline for donor event notification is too short

Volunteers don't want to travel to Federal Way and Tacoma

# data[].attributes.body
Current:

1. Different Dev Staff meeting multiple time with Nicola each month

2. Requests made when needed

3. Limited lead time for requests

4. No training on how to use request system

5. Dev team members change priorities after plans have been set

6. Lack of Clarity about audience

# data[].attributes.body
Events are calendared months in advance

Dev and Ed Team clarity about needs and opportunities

Robust team of volunteers ready to engage

Dev Team knows volunteer strengths and can match to opportunities

Accurate tracking of Volunteer and Hours

Robust Donor Stewardship and Appreciation

# data[].attributes.headline
How do we Get Full Information About Events in Advance

# data[].attributes.subject
How do we Get Full Information About Events in Advance

# data[].attributes.headline
Who Can Give the 360 View of Ed Department 

# data[].attributes.subject
Who Can Give the 360 View of Ed Department 

# data[].attributes.body
Information Shared on an As Needed Basis

Duplication of Efforts

Too Many One Off Asks of Marketing Team

Team Members create

Multiple Relationships with Donor/Corps. Are we coordinating?

# data[].attributes.body
1. Known cadence of meetings with MarComms Staff

2. Team uses MarComms tools for requests

3. Audience Clarity

4. Knowledge of Usable assets - Libraries are up to date

# data[].attributes.body
Too reactive

No SWOT analysis or landscape analysis for new initiatives

Luncheon takes priority over other projects

Are We Pausing Enough?

# data[].attributes.body
Plans can be siloed

Plans change at last minute

No feedback sessions

# data[].attributes.body
Current State - We don't understand the magnitude of their work.

# data[].attributes.body
How are they connecting with local/regional media

# data[].attributes.body
Team is in agreement of what we're doing and why - target audience, goal, etc. Clear metrics

Theory of Change for Projects

# data[].attributes.headline
Higher Level Inter-Team Planning and Sharing

# data[].attributes.subject
Higher Level Inter-Team Planning and Sharing

# data[].attributes.body
Organizational protocol for sharing and collaboration, i.e. - Volunteers.

When other teams don't share information, we lose opportunities to connect.

How are we collaborating with Troy for Data. -- holistic view

# data[].attributes.body
Team Understands Priority Programs for Funding

Lack of Information about school capabilities makes i it difficult for TY to fundraise

# data[].attributes.body
Plans shared with team

Team can provide input, but clear roles and decision makers

Adequate lead time for data - build this into the plan timeline

Reports are clear on assets required (include kind of information/data needed and why)

Define KPI's as part of Proposal/Project plan