META
AI's challenge wasn't intelligence
It was collaboration.
I built an AI-powered workflow that turned scattered work into shared updates—making team communication easier and more connected.
0
%
EST. TIME SAVED
Claude + MCP
AI ORCHESTRATION
Multi-source
CONTENT SYNTHESIS
ROLE
Product Designer & Builder
SCOPE
AI Experience & Prototyping
TIMELINE
2026
0
%+
EST. TIME SAVED
Claude + MCP
AI ORCHESTRATION
Multi-source
CONTENT SYNTHESIS
ROLE
Product Designer & Builder
SCOPE
AI Experience & Prototyping
TIMELINE
2026

The Opportunity

At Meta, posts helped teams share progress and priorities. But preparing weekly updates meant piecing together information from calendars, documents, and conversations—time taken away from the work itself.

Rather than introduce another communication tool, I chose to use AI to make participating in Meta's existing posting culture easier.

We had the tools to communicate. Participation still took work.

From Scattered Work to Shared Understanding

I designed a Claude- and MCP-powered workflow that synthesized existing work context into structured weekly updates.

Individuals could then refine the message, verify references, and decide what to share.

Less effort to communicate. More opportunity to connect.

SYSTEM ARCHITECTURE
This is some text inside of a div block.

Inputs

Calendars, tasks, documents, and collaborators provide work context.

This is some text inside of a div block.

Claude + MCP

AI synthesizes context into structured updates with relevant references.

This is some text inside of a div block.

Human review

People refine the message, verify details, and approve sharing.

This is some text inside of a div block.

Post

A shared post keeps teammates informed, aligned, and connected.

THE OUTPUT

What the system produced

Each update combined a weekly synopsis, workstream priorities, supporting documents, and relevant collaborators in a format colleagues could quickly scan.

THE OUTPUT · CONCEPTUAL RECONSTRUCTION
Kendrick Dean
2h • ABC Team

Weekly Tasks & Priorities

Apr 21 - Apr 25 2026

TL;DR

This week, we finalized key design flows, identified usability improvements, and aligned teams on delivery priorities. Next week, we'll refine the experience, validate changes with stakeholders, and prepare for engineering handoff.
01.

Product Delivery

Completed key design flows for the upcoming release and aligned with engineering on implementation priorities.
• Finalized account overview prototype.
• Resolved accessibility feedback.
• Prepared designs for engineering handoff.
02.

Research & Feedback

Usability testing revealed opportunities to improve navigation, task clarity, and the overall experience.
• Completed five user interviews.
• Identified three recurring usability issues.
• Prioritized improvements for the next iteration.
03.

Team Alignment

Aligned product, design, and engineering teams on upcoming milestones, dependencies, and delivery priorities.
• Confirmed ownership of key deliverables.
• Resolved outstanding design dependencies.
• Coordinated next steps across teams.
04.

Future Priorities

Focus on refining the experience, validating improvements, and preparing the next release milestone.
• Finalize revised navigation and task flows.
• Review prototype updates with stakeholders.
• Complete design QA and
handoff documentation.
Related links

Spinbot Design Handoff Checklist (Doc)

Project Key Usability  Report (Doc)

Tagged collaborators

Alex Rivera

Jordan Jon

Priya Nair

The names, project details, and supporting documents are fictional.

Adoption & Impact

What began as a design-team workflow spread to engineering, product management, and research—without a formal mandate.

In my experience, weekly updates went from roughly 45 minutes of preparation to 5 minutes with AI, including review and edits—an estimated 89% time savings.

Built for designers. Useful beyond design.

One Framework. Many Implementations

sasa

Making the Framework Transferable

Scaling beyond the original team meant making experience standards actionable across products and organizations.

A reusable experience template, cross-functional alignment, and ongoing design leadership helped translate those standards into new implementations—without compromising the experience's core.

HOW THE FRAMEWORK ENABLED SCALE
01

Reusable experience template

Codified required elements and allowable variations across products, policies, and entities.

02

Expansion leadership

Directed conceptual design, cross-functional alignment, research validation, and execution.

03

Executive alignment

Co-defined the strategic narrative that helped resolve launch barriers, including for Instagram.

EVIDENCE OF RESPONSIBLE SCALE

Responsible expansion delivered measurable value.

What I Carried Forward

Leading the experience from MVP through subsequent refinements taught me to balance customer needs, business priorities, and technical constraints without losing sight of usability.

That perspective shaped how I approach product challenges today: establish direction, make deliberate tradeoffs, and use evidence to continually improve the experience.

A useful product isn't defined by how much it can do, but by how confidently people can use it.

Technology can make communication easier without necessarily bringing people closer together.

This experience reinforced my belief that AI should do more than accelerate tasks. It should reduce the friction that prevents people from participating and connecting.

Efficiency was the mechanism. Connection was the goal.