agile# Running a Small Healthcare Scale-Up? Try This Old-School Team Strategy (1/8)
Running a small healthcare scale-up with a distributed team is tough. You're building B2B2C products, juggling time zones, and trying to keep everyone aligned without burning people out. Akio Morita, co-founder of Sony, didn't have Slack or Zoom—but he built global teams that moved fast by focusing on shared purpose, not just tools. His approach lines up perfectly with Feature-Driven Development (FDD). Here's how his mindset can help your small team collaborate better across distances. (2/8)
Morita believed that great products come from small, empowered teams who deeply understand the end user—even when they're far apart. At Sony, engineers weren't just building gadgets; they were solving real human problems. In B2B2C healthcare, your product touches both providers and patients, so clarity on user needs is non-negotiable. His method wasn't about micromanaging—it was about giving teams clear ownership of features, fast feedback, and room to adapt. (3/8)
Here's how to put this into practice with your team:
1. Start with a shared why for each feature. Before any sprint, hold a 30-minute async video call (recorded for time zones) where each team member explains how their piece connects to patient or provider outcomes. No slides—just plain talk. This mirrors Morita's habit of grounding every project in real-world impact. (4/8)
2. Break work into 2-week FDD-style features. Each feature should be small enough for one person to own end-to-end. For example: Enable clinic staff to reschedule patient appointments via mobile. Keep it concrete. Small teams thrive when scope is tight and ownership is clear. (5/8)
4. Build feedback loops into every iteration. After each feature ships, get input from at least one real user (a nurse, a clinic admin, a patient advocate). Don't wait for a big review—ask early, adjust fast. Morita tested Walkman prototypes on Tokyo streets before finalizing design.
5. End each sprint with a 15-minute retro focused on collaboration, not code. Ask: Where did distance slow us down? What helped us stay aligned? Then pick one small process tweak for next time. (7/8)
When your team owns features, talks plainly, and learns from real users every two weeks, distance stops being a barrier—and starts being just another variable to design around. Try this for one sprint, then share what worked (or didn't) with the rest of us.
#HealthcareStartups #RemoteTeams #FeatureDrivenDevelopment #DistributedWork #B2B2C #AgileHealthcare #SmallTeamBigImpact #AsyncCollaboration #ProductDevelopment #TeamAlignment (8/8)