A command centre to centralize brand assets and tools using AI agents
OVERVIEW
Project Bloom is an AI-driven platform that helps businesses manage brand assets and optimize operations. It centralizes data, automates tasks, and ensures brand consistency across teams.
The platform integrates with over 250 tools and provides AI agents for various functions like marketing and HR, enhancing efficiency and reducing manual work. You can explore Project Bloom more (https://www.projectbloom.io).
ROLE & DURATION
UX/UI Design Lead
Heavy involvement in overseeing the design direction of the platform, ensuring that user experiences are intuitive and engaging.
Collaborated with the dev teams to maintain brand consistency, enhance usability, and create an interface that meets both functional and aesthetic needs.
Led and guided the design team, aligning the UI with the overall product vision while optimizing user flows and interactions.
Team consisted of: UX/UI Designer - CEO - Project Manager - Software engineer- Full Stack Developers - Content writers - Sales
Jan 2024 - Ongoing
WHAT IS PROJECT BLOOM
ProjectBloom is an AI platform that connects & centralizes your data and maximizes operational efficiency through trained AI Agents using OpenAI, Claude 3, Anthropic, Gemini, Meta.ai, and others.
MISSION POINTS
-
Crisis Management Response
-
Creative Direction Initiative
-
Brand Consistency Campaign
BUSINESS GOAL
To communicate how ProjectBloom.io centralizes brand data and deploys AI Agents like Agent Bloom to manage single and multi-brand operations.
KEY CONSIDERATIONS
-
To create a simple, intuitive navigation designed to convert to demos or registrations.
-
To use animations or interactive elements to showcase AI capabilities.
-
To Include a demo video or interactive tour of the platform.
-
To stay consistent with the use of the logo, fonts, and colors from the brand kit.
-
To reflect the tone of voice in all copy. Spy talk as Agent Bloom is the Chief of Staff for the Command Center.
discovery & research
For Project Bloom, the key user personas revolve around agencies and teams that need a centralized hub for managing their brand assets. Here are the primary user personas:
1. Brand Managers
Oversee brand consistency, and a structured platform is needed to store, update, and share brand assets across teams.
2. Marketing Teams
Use the platform to access and deploy brand assets efficiently across campaigns, social media, and advertising.
3. Designers & Creatives
Require a well-organized asset library to ensure all visuals, logos, and brand guidelines are easily accessible and up to date.
4. Agency Owners & Executives
Need a high-level overview of how brand assets are managed and ensure teams follow brand guidelines.
5. Developers & Product Teams
Utilize brand assets within digital products and need a seamless way to integrate them into their workflows.
6. Clients & External Partners
Access brand assets for co-branded initiatives, ensuring brand consistency across external collaborations.
One Main User Journey
Sarah, a marketing manager at a growing startup, constantly struggles to keep her team aligned. Content calendars are scattered across multiple tools, and team members often miss updates about published assets or scheduled events.
She wastes time chasing people for confirmations, while admins like her find assigning tasks or managing roles difficult. The chaos grows with every new campaign — files go missing, deadlines are unclear, and no one is ever sure who’s doing what.
That’s why Project Bloom was born—to centralize communication, streamline content and calendar management, and give teams the clarity and control they need to thrive rather than survive.
Internal User Testing Results - Marketing & Design Departments
Sample size: 15 team members
Departments involved: Social Media (5), Design (5), Account Management (5)
Would you find Project Bloom useful for your daily workflow?
-
Yes:
-
Maybe, depending on features:
-
No:
87%
0%
13%
Would it improve communication around content calendars and events?
-
Yes, significantly:
-
Somewhat:
-
Not really:
73%
20%
7%
Do you currently struggle with scattered assets and unclear responsibilities?
-
Yes:
-
Occasionally:
-
No:
93%
7%
0%
Would having role-based access and team management tools help you stay more organized?
-
Yes:
-
Maybe:
-
No:
13%
7%
80%
Favorite feedback snippets:
-
“Finally, a way to stop asking, ‘Who uploaded this version?’ every day.”
-
“If it sends real-time notifications, it’s a game changer.”
-
“As an account manager, I need visibility into everything, this could save me hours a week.”
-
“Please tell me it integrates with our current tools!”
HOW MIGHT WE
How might we help teams stay aligned, informed, and organized by centralizing content calendars, asset management, and team communication — all in one intuitive platform?
challenges
1. Defining the User Experience for a Complex SaaS Platform
This type of platform often served diverse user groups with varying needs and technical expertise. Balancing simplicity and advanced functionality was tricky.
3. Designing for Scalability & Flexibility
Ensured the design could scale and remain flexible as new features were added, without compromising the user experience or requiring frequent redesigns.
5. Adapting to Agile & Continuous Iterations
Frequent changes and new requirements had sometimes disrupted the design process.
7. Handling Complex Workflows & Data Visualization
The platform often required dashboard redesigns, added integrations, and intricate user flows, which can overwhelm users if not designed well. Therefore, having a focal point to simplify the flow was my priority.
9. Handling Developer Constraints & Technical Limitations
2. Managing Cross-Functional Collaboration
Communicating design decisions was challenging due to differing visions, but I ensured alignment by considering all input and choosing the best design solution.
4. Ensuring Accessibility & Usability Standards
Making the platform accessible while maintaining visual appeal and responsiveness across devices was challenging when optimizing the visuals of tables and calendars on mobile versions.
6. Keeping Users Engaged & Reducing Churn
Retaining our users by providing intuitive onboarding experiences that are simple and straightforward was our priority. Therefore, multiple attempts at structuring the flow occurred.
8. Ensuring a Smooth Handoff & Post-Launch Support
Post-launch issues like bugs, inconsistencies, or missing features impacted the user experience, which disabled a mirrored view of the actual design files.
Some design elements were not feasible due to backend limitations or development timelines, which affected my flexibility in designing.
Actively shaping the design
Project Bloom came to life through focused design work and continues to evolve through ongoing development and refinement.
UNDER DEVELOPMENT
What to Look Forward To.
