Data Dashboard for Strategic Planning
🚨 Problem
Amid rapid growth, The Transformations Community does not have data to strategically plan initiatives that are effective and engaging to its community
💡 Solution
A data dashboard presenting areas of engagement for community members across various platforms
💼 Roles: UX Designer, Data Analyst
Impact
Data dashboard created digestible customer insights; thus shaping the creation of future projects, further defining brand identity
Before
After
“This is great for creating more targeted initiatives and seeing our growth.”
Opportunities to Utilize Data
🐒 Mailchimp Newsletters & Campaigns
Monthly newsletters and additional campaigns sent out through Mailchimp already contained lots of un-utilized data
🤳 Social Media
LinkedIn and X accounts had significant growth, but no data was being utilized to create intentional interactions with community members
🌐 Website
Website had no advanced tracking, missing out on user data and areas to improve awareness and performance.
Selecting Metrics
Selected metrics that best inform future planning. Interviewed members of management, web, and marketing teams to determine most useful analytics when planning.
Building The Data Pipeline
Considered how data could be collected and the platform to consolidate metrics.
File Structure
Created Information Architecture system for how document would be structured with a specific focus on different user-groups and how each group would use document.
Data Dashboard
The final product divided the data up by user group and highlighted areas that were growth and deterioration.
Reflection
Defining Compelling Metrics
Determining the right metrics to track was a big obstacle in this project. Lacking prior experience with non-profit planning, I had to identify metrics that would be valuable to various user groups and impactful for the organization. To address this, I collaborated closely with upper management and marketing, gaining insights into how metrics influence funding, budgeting, and organizational growth.
Considering Data in Tech Stack Design
Implementing this pipeline was particularly difficult due to the array of data sources, each requiring cleaning and calculations. While I had a clear vision of the endpoint—a Looker Studio report—and the starting points, the real challenge lay in connecting these vastly different sources. This required significant technical effort to clean and prepare the data for compatibility with Looker Studio. Through this process, I learned the importance of accounting for data and tracking systems when building an organization's tech stack, ensuring seamless integration with both the stack and reporting tools.