Patrimonio Hoy: Microfinance program for low-income homebuilders
How a 3-Day Design Sprint Solved 6 Critical Problems for 10,000+ Low-Income Homebuilders
Facilitating a remote Design Sprint to align stakeholders, prioritize pain points, and prototype a mobile app that made construction financing accessible for underbanked communities in Mexico.
3-day remote Design Sprint + user testing
Design Sprint Facilitator & Prototyper
CEMEX Innovation Department (Mexico)
Key Metrics
3 Days
70+ Problems
6 Prioritized Solutions
5 Users Tested
10K+ Downloads
The Problem
When CEMEX's Innovation Department reached out, their request was straightforward: "Teach our Patrimonio Hoy team UX principles so they can build an app for our partners."
But I saw a different opportunity.
Instead of delivering theoretical workshops, I proposed co-creation: facilitate a Design Sprint where stakeholders would build the solution themselves, using their deep domain expertise while I guided the process. This approach would kill two birds with one stone, create a validated solution while teaching UX through practice.
The Strategic
Pivot
Understanding Patrimonio Hoy
Patrimonio Hoy is CEMEX's microfinance program that enables low-income families in Mexico to build or improve their homes through:
The program serves thousands of families who are largely excluded from traditional banking systems.

The Challenge
The Patrimonio Hoy team wanted to create an app for their partners (called "socios"), but faced critical barriers:
Organizational Challenge:
User Complexity:
Operational Friction:
The Patrimonio Hoy team wanted to create an app for their partners (called "socios"), but faced critical barriers:
The team knew they needed a digital solution, but lacked alignment on where to start.
Process
Phase 1: Alignment Workshop (Day 1)
We kicked off with Expert Interviews a Design Sprint exercise where each stakeholder documented pain points they'd observed from socios, internal teams, and operational data.
The Exercise: Each participant framed problems as "How Might We" (HMW) questions, creating a shared language for discussing opportunities.

Communication & Accessibility
Transparency & Trust
Process Friction
Engagement & Motivation
Key Insight
The team discovered patterns they hadn't seen before. What they initially framed as "operational issues" were actually visibility problems, “socios” couldn't see their progress, understand their payments, or track their project status.
Output: 70+ HMW questions across four major themes:
Process
Phase 2: Solution Workshop (Day 2)
With 70+ opportunities identified, we needed to focus. I facilitated a prioritization session using dot voting.
The Method:

The 6 Prioritized Challenges:
With priorities clear, we mapped the end-to-end user journey—from discovering Patrimonio Hoy through completing a construction project and potentially restarting.
PROGRESS TRACKING & ENGAGEMENT
Socios lost motivation mid-project and didn't prioritize home improvement.
PROJECT COMPLETION &
RE-ENGAGEMENT
After finishing one project, socios didn't return for additional home improvements.
MATERIAL REQUEST & DELIVERY TRACKING
Material ordering was manual, slow, and lacked transparency on pricing and delivery.
ADVISORY SERVICE REQUEST & TRACKING
Scheduling technical advisory (Asesoría de Vivienda) was slow and opaque.
PAYMENT TRACKING & TRANSPARENCY
Socios couldn't see their payment progress, causing confusion and disengagement.
DISCOVERY & ONBOARDING
Socios needed clarity on what Patrimonio Hoy offers before committing to weekly payments.
This collaborative mapping surfaced critical touchpoints where the app could add value.
Process
Phase 3: Decision Workshop (Day 3)
I translated the user flows into a medium-fidelity prototype, designing features that directly addressed each prioritized challenge.
Core Features Designed:
1. Self-Service Payments
2. Material & Advisory Scheduling
"Mi Objetivo" Progress Dashboard
"Mi Objetivo" Progress Dashboard
Proactive Notification System
Proactive Notification System
Transparency Features
Service Ratings & Feedback






Validation
User Testing with Real Socios
Before finalizing the prototype, I conducted testing sessions with 5 real Patrimonio Hoy socios—the actual users who would depend on this app.
Testing Method: Remote prototype walkthroughs with structured feedback sessions focused on usability and value perception.
What We Learned
What Resonated Most:
"Being able to see my loan status, what I owe, and this week's payment—that's what I need most."
The transparency features struck a chord. Socios valued visibility into their financial status above all else—confirming our insight from Day 1 that this was fundamentally a visibility problem.
All 5 participants said they would use the app, with one critical condition: it had to run on their low-end devices.
Critical Constraint Discovered:
The majority of socios were unbanked, meaning they didn't have credit or debit cards. The digital payment feature, while desired, wouldn't work for most users in the near term.
Impact &
Outcomes
Immediate Results
Stakeholder Alignment Achieved:
Validated Prototype Delivered:
De-Risked Development:
Reflections
& Learnings
Why Design Sprint Over Training?
When the Innovation Department requested UX training, I saw an opportunity to deliver something more valuable: action over education.
The team possessed deep domain expertise about Patrimonio Hoy, their socios, and operational realities. They didn't lack knowledge—they lacked a framework to channel it into prioritized action.
By facilitating co-creation through a Design Sprint, we:
Business Value Created:
By facilitating co-creation instead of delivering training workshops, we:
De-Risked Development:
Patrimonio Hoy: Microfinance program for low-income homebuilders
How a 3-Day Design Sprint Solved 6 Critical Problems for 10,000+ Low-Income Homebuilders
Facilitating a remote Design Sprint to align stakeholders, prioritize pain points, and prototype a mobile app that made construction financing accessible for underbanked communities in Mexico.
3-day remote Design Sprint + user testing
Design Sprint Facilitator & Prototyper
CEMEX Innovation Department (Mexico)
Key Metrics
3 Days
70+ Problems
6 Prioritized Solutions
5 Users Tested
10K+ Downloads
The Problem
When CEMEX's Innovation Department reached out, their request was straightforward: "Teach our Patrimonio Hoy team UX principles so they can build an app for our partners."
But I saw a different opportunity.
Instead of delivering theoretical workshops, I proposed co-creation: facilitate a Design Sprint where stakeholders would build the solution themselves, using their deep domain expertise while I guided the process. This approach would kill two birds with one stone, create a validated solution while teaching UX through practice.
The Strategic
Pivot
Understanding Patrimonio Hoy
Patrimonio Hoy is CEMEX's microfinance program that enables low-income families in Mexico to build or improve their homes through:
The program serves thousands of families who are largely excluded from traditional banking systems.

The Challenge
The Patrimonio Hoy team wanted to create an app for their partners (called "socios"), but faced critical barriers:
Organizational Challenge:
User Complexity:
Operational Friction:
The Patrimonio Hoy team wanted to create an app for their partners (called "socios"), but faced critical barriers:
The team knew they needed a digital solution, but lacked alignment on where to start.
Process
Phase 1: Alignment Workshop (Day 1)
We kicked off with Expert Interviews a Design Sprint exercise where each stakeholder documented pain points they'd observed from socios, internal teams, and operational data.
The Exercise: Each participant framed problems as "How Might We" (HMW) questions, creating a shared language for discussing opportunities.

Communication & Accessibility
Transparency & Trust
Process Friction
Engagement & Motivation
Key Insight
The team discovered patterns they hadn't seen before. What they initially framed as "operational issues" were actually visibility problems, “socios” couldn't see their progress, understand their payments, or track their project status.
Output: 70+ HMW questions across four major themes:
Process
Phase 2: Solution Workshop (Day 2)
With 70+ opportunities identified, we needed to focus. I facilitated a prioritization session using dot voting.
The Method:

The 6 Prioritized Challenges:
With priorities clear, we mapped the end-to-end user journey—from discovering Patrimonio Hoy through completing a construction project and potentially restarting.
PROGRESS TRACKING & ENGAGEMENT
Socios lost motivation mid-project and didn't prioritize home improvement.
PROJECT COMPLETION &
RE-ENGAGEMENT
After finishing one project, socios didn't return for additional home improvements.
MATERIAL REQUEST & DELIVERY TRACKING
Material ordering was manual, slow, and lacked transparency on pricing and delivery.
ADVISORY SERVICE REQUEST & TRACKING
Scheduling technical advisory (Asesoría de Vivienda) was slow and opaque.
PAYMENT TRACKING & TRANSPARENCY
Socios couldn't see their payment progress, causing confusion and disengagement.
DISCOVERY & ONBOARDING
Socios needed clarity on what Patrimonio Hoy offers before committing to weekly payments.
This collaborative mapping surfaced critical touchpoints where the app could add value.
Process
Phase 3: Decision Workshop (Day 3)
I translated the user flows into a medium-fidelity prototype, designing features that directly addressed each prioritized challenge.
Core Features Designed:
1. Self-Service Payments
2. Material & Advisory Scheduling
"Mi Objetivo" Progress Dashboard
"Mi Objetivo" Progress Dashboard
Proactive Notification System
Proactive Notification System
Transparency Features
Service Ratings & Feedback






Validation
User Testing with Real Socios
Before finalizing the prototype, I conducted testing sessions with 5 real Patrimonio Hoy socios—the actual users who would depend on this app.
Testing Method: Remote prototype walkthroughs with structured feedback sessions focused on usability and value perception.
What We Learned
What Resonated Most:
"Being able to see my loan status, what I owe, and this week's payment—that's what I need most."
The transparency features struck a chord. Socios valued visibility into their financial status above all else—confirming our insight from Day 1 that this was fundamentally a visibility problem.
All 5 participants said they would use the app, with one critical condition: it had to run on their low-end devices.
Critical Constraint Discovered:
The majority of socios were unbanked, meaning they didn't have credit or debit cards. The digital payment feature, while desired, wouldn't work for most users in the near term.
Impact &
Outcomes
Immediate Results
Stakeholder Alignment Achieved:
Validated Prototype Delivered:
De-Risked Development:
Reflections
& Learnings
Why Design Sprint Over Training?
When the Innovation Department requested UX training, I saw an opportunity to deliver something more valuable: action over education.
The team possessed deep domain expertise about Patrimonio Hoy, their socios, and operational realities. They didn't lack knowledge—they lacked a framework to channel it into prioritized action.
By facilitating co-creation through a Design Sprint, we:
Business Value Created:
By facilitating co-creation instead of delivering training workshops, we:
De-Risked Development: