Tommy Shelby returns. A Peaky Blinders Film starring Cillian Murphy is coming to Netflix.
“It seems like Tommy Shelby wasn’t finished with me…It is very gratifying to be recollaborating with Steven Knight and Tom Harper on the film version of Peaky Blinders. This is one for the fans.”
still thinking about the engineer who built a frontend of Reddit that makes it look like you're on Outlook at work
human ingenuity truly knows no bounds
@GekGemu I was actually reading through these last night! I think it was insightful tbh. One of them hit a little too close to home, but I had gone to the doctor for it so I can sleep easy.
Startup vs Big Company Dynamics
Startup
• Observation: Users want a new feature.
• Designer (60 min later): Here are some figma prototypes.
• Engineer: We can ship this by the end of the week.
Big Company:
• Observation: Let’s discuss our observations when Suzy’s back; targeting end of month.
End of Month: Bob should really be in this meeting, let’s reschedule.
• Meeting: Users want this feature. We’ll need Jessica's buy-in.
• Jessica Meeting: Presented six weeks of research for the new feature.
• Jessica: This can fit into our H2 planning.
• H2 Kickoff: Remember users want this feature?
• Product Manager: Will draft a product brief that will be ready for H2's second cycle.
• Designer: Drafted designs in Figma, ready for the next review.
• Design Review: Why this feature? Should we prioritize X instead?
• Outcome: Feature sidelined. Cycle repeats.
**Note** This isn’t subtweeting but the reality of software development at scale. Whether you're a startup or a big company, it’s crucial to streamline to avoid this. Success breeds complexity, but no startup is immune.
@Kraytoshi It pains me that I knew about Figma in its infancy and didn’t give it much attention. I could have been an early adopter but I used it briefly and then went right back to Adobe. Now I’m a huge advocate for them to any designer I come across not using it.
I often find I tune out during podcasts but this episode had my attention end to end. Mihika's perspective is so validating (even vindicating) to my own pipeline, where I've previously been told I jump into prototyping too soon. The Figma product team's conviction >
Mihika Kapoor (@mihikapoor) is a superstar PM at @Figma where she’s known as the go-to person for leading new 0-to-1 products. She was an early PM on FigJam, is currently leading a new (undisclosed) product that’s launching at Figma's Config conference this year, and is beloved by everyone who works with her.
In our conversation, we discuss:
🔸 Advice for taking ideas from 0 to 1 at larger companies
🔸 How to craft a compelling vision
🔸 How to tactically communicate your vision
🔸 The importance of vulnerability and feedback
🔸 Advice for building a strong team culture
🔸 Pivoting priorities with grace and enthusiasm
🔸 AI and its impact on PMs
🔸 Much more
Listen now 👇
YouTube: https://t.co/V7F7CvL7of
Spotify: https://t.co/XNJt3o4eed
Apple: https://t.co/2HRfzjbAl1
Key takeaways:
1. Putting ideas out there, even if they are wrong, can lead to better solutions and more productive discussions. It’s not just about having a great idea or building a prototype; it’s about actively engaging and rallying others around that idea to create momentum and excitement. Whether it’s pitching ideas at events like hackathons or simply asking colleagues for assistance, the key is to not let perceived limitations hold you back from pursuing your vision.
2. Mihika likens the role of a 0-to-1 team within a large company to that of Hestia in Greek mythology, who is the “keeper of the hearth.” It is Hestia’s job to always keep the hearth burning, even while other gods go out on separate quests. This means always keeping the 0-to-1 project alive and helping it spread to others, mostly through setting vision and building hype.
3. To set the vision for a new idea, ask: “If I and my team do our job correctly, what does the world look like?” Then convey the pain point, solution, and proof in a format that can “show, not tell” stakeholders what you’re doing. For example, use prototypes, Figma mock-ups, and customer testimonials.
4. Internal hackathons are a great way to encourage innovation. Figma has a Maker Week where the entire company—including technical and non-technical employees—goes on pause for a week to work on ambitious ideas. Maker Week and other internal hackathons have led to many successful Figma products, including Jambot and Figma’s entire widget platform.
5. Figma implements a fun “hot seat” tradition, where each person takes turns being in the hot seat for a set amount of time. During their turn, the person can be asked anything by the other members of the group. By understanding what motivates each team member and building strong relationships, collaboration becomes more effective, leading to a more enjoyable work environment and ultimately better outcomes for the product or project. The key is to create a comfortable and friendly atmosphere where everyone feels open to sharing.
6. Make time for fun! “Play” is one of Figma’s core values, and Mihika makes a concerted effort to have enjoyable team gatherings. When people have fun together, they get to know each other more deeply and can feel more appreciated within the group. One tradition Mihika’s team uses is “The Figgies.” The team gathers to give out absurd awards for things like “most likely to go their entire career without writing a PRD.”