Core Story Set

Leading Fabric's early development required building a strong team while managing limited resources. I focused on creating clear systems for accountability and collaboration. I set up weekly team meetings for updates, studio hours for focused work time, and one-on-ones to track progress. Instead of just telling people what to do, I helped them think through problems by asking questions that guided them to solutions. When team members asked "what should I do?", I responded with "what do you think would have the biggest impact?" This approach worked well. The team stayed together through our critical early phases. Everyone started taking more ownership of decisions. We built momentum while keeping our focus on what matters - using technology to help people connect in real life.

We were having issues with our iOS development in Swift. It was taking too long to build features, and onboarding new developers was difficult. So, I took the initiative and researched better solutions and found Expo could help us move faster. I tested it by building a small prototype to prove it would work. Then I made a clear plan for switching our development approach. I walked the team through the benefits - faster development, easier testing, and simpler onboarding for new team members. The change to Expo made a big difference. We started shipping features much faster. New developers could get started more easily. This showed my ability to spot problems early and fix them before they slow us down.

The Red Team helps us test new features before rolling them out to all users. When debating our latest "What's the Move" feature, I needed to understand what would actually help people coordinate informal hangouts. Rather than just guessing, I analyzed feedback from Red Team testing and user interviews. The data showed people want a super lightweight way to gauge interest before creating a full event. This insight led us to strip down the feature to just require a title at first - no date, location, or other details needed. Once enough friends show interest, then they can turn it into a real event. This data-driven approach helped us stay focused on what users actually need rather than overcomplicating things. We're now validating this simpler version with the Red Team before spending more development time on extra features.

As Fabric grew, we started having issues with team communication. People weren't always clear on priorities or project status. I fixed this by setting up a simple but effective system. We now have three key meetings: weekly full team updates on Thursday, product planning on Monday, and daily "Let's Accelerate" sessions for collaborative work. I also made sure every team member has regular one-on-ones with their manager. We use Jira to track tasks and Google Workspace for documentation. These changes made a real difference. Projects move faster because everyone knows what's happening. Team members understand their priorities and feel more connected to our goals. The system scales well as we grow while keeping things clear and organized.