Personal support-system concept
NICU4U did not begin as a design project. It began as a system I built to survive my daughter's 100-day stay in the neonatal intensive care unit.
Problem
During my daughter's stay, I started building systems to answer questions that nobody could easily answer.
The problem was not a lack of information. The problem was trying to process, organize, remember, and communicate critical information under prolonged stress - while working, while finishing school, while my wife and I were both exhausted and afraid.
The NICU is not a single information screen. It is a rotating cast of doctors, nurses, and specialists, each responsible for a different part of your child's care, handing off to each other across shifts while you try to keep up.
Primary evidence
The concept grew from a 100-day NICU stay, 578 feeding logs, growth tracking, pumping-output records, question lists, communication notes, and forecast models built to make uncertainty easier to reason about.
Where NICU4U started
I did what I always do under pressure: I started collecting data.
I pulled my daughter's medical records each week and built a tracking system in Excel: feeding times, volumes, daily totals, weight measurements, growth predictions, and questions we needed to carry into care conversations.
I also tracked pumping output alongside intake because numbers gave us something more useful than vague reassurance. That coping system became the foundation for NICU4U.
System model
Explain where the baby is in the care journey and what changed recently.
Make updates, terms, and next steps understandable without oversimplifying care.
Help Emily, James, and Nadia keep questions and updates from fragmenting.
Clarify what can be answered in-app and what belongs with the care team.
Process artifacts
I framed NICU4U as a communication system around the Torres family and their nurse, not as a medical dashboard. The design question became how to reduce repeated explanation burden while keeping clinical authority with the care team.
I used the Torres family as a design frame to generalize what I had experienced personally. Emily is the primary caregiver managing daily information. James is a secondary caregiver trying to stay oriented across gaps. Nadia is the nurse fielding repeated questions across shifts. These are not fictional problems - they are the communication patterns I observed firsthand and then abstracted into a design model.
Tracking artifacts
Ten tracking sheets. One hundred days of data. Five hundred and seventy-eight individual feedings logged. Three custom forecast models built to predict my daughter's growth trajectory and measure how far off my estimates were. My wife's pumping output tracked daily alongside my daughter's intake so we could see - with actual numbers - that supply was keeping pace. This is not a design research artifact. This is what I built during one of the hardest periods of my life, using the only tools I had available.
Real artifact restoration
Progressive disclosure, calm notification tone, no false reassurance, emotional readability, and clear escalation back to the care team.
Daily summaries, term explanations, milestone tracking, guided questions, shared updates, and discharge preparation support.
Hi-fi prototype direction
These screens translate the journey-map findings into parent orientation: what changed, what matters now, what is coming next, and what should be asked during care conversations.
Plain-language translation
The Learn screens are important because NICU confusion often comes from translating equipment, procedures, roles, and bedside language into something parents can use in the moment. The goal is not to replace clinicians. It is to help parents arrive at rounds with better questions.
Explain what it is, why it may matter, what parents might hear during rounds, and one useful question to ask.
The app can prepare parents for a conversation. It should not turn educational content into clinical advice.
Question and care-team loop
This flow turns parent questions into a shared object that can be saved before rounds, assigned to the right care role, answered in plain language, and marked for follow-up instead of disappearing into memory.
Family support loop
NICU4U2 separates approved family updates, practical help, lightweight encouragement, and access control. That matters because family support can become another communication job when parents are already depleted.
Clinical review boundary
The staff-facing concept is included as a boundary artifact: parent-facing summaries, shared updates, and round questions need review rules, audit history, and permissions before they can enter a real clinical workflow.
What shaped the system
Problem: Emily, James, and Nadia experience the same care moment from different informational positions.
Decision: Map the product around handoffs among the primary parent, secondary parent, and nurse.
Rationale: The support problem is not just what one parent knows; it is what has to be repeated, clarified, and trusted across the group.
Tradeoff: The concept becomes less like a simple app screen set and more like a service model that needs clinical review.
Problem: Clinical structures do not match the way stressed parents seek information.
Decision: Frame content around what parents are trying to understand or do.
Rationale: A support product should reduce translation work.
Tradeoff: The system needs careful clinical review before real deployment.
Design walkthrough
Maps admission, daily care, questions, setbacks, and discharge preparation through actions, thoughts, communication strain, and opportunities.
Shows where uncertainty accumulates across time instead of treating the NICU as one information screen.
The journey map shifted the project toward communication breakdowns and repeated explanation burden.
Organizes questions around what changed, what matters now, who can answer, and what the family needs to ask next.
Helps parents preserve questions before rounds or bedside updates.
The flow prioritizes clarity and handoff support over adding more medical content.
Frames repeated questions and unresolved concerns so nurses can see what has already been explained.
Reduces the loop of Emily asking, James missing context, and Nadia needing to repeat the same explanation.
The concept became a communication support system rather than a generic parent education app.
Research / testing
Persona development, Torres family journey mapping, information hierarchy critique, and support-flow modeling.
The project frames NICU support as a layered communication system: what changed, what matters now, questions to ask, and who should answer.
Outcome
Reflection
This project sharpened something I already suspected: the hardest UX problems are not interface problems. They are coordination problems - moments where the right information exists somewhere in the system but cannot reach the person who needs it, at the moment they need it, in a form they can act on.
I lived that problem for 100 days. I built manual systems to manage it. And then I designed a product concept to address it - not because it was an interesting design challenge, but because I knew exactly what it felt like to need it.
The strongest next version of NICU4U involves clinical stakeholder review, nurse workflow research, and parent feedback sessions with families currently in care. The concept is credible when it stays focused on communication strain. It becomes dangerous if it ever implies it can reduce medical uncertainty itself.
That distinction - between managing information and managing outcomes - is one I understand personally, not just professionally.