1
0 Comments

Introducing Strome - Update #0

Hi, I’m Piers, an engineering leader with years of experience helping remote product engineering teams deliver meaningful work consistently. Over the years, I’ve led teams through early growth phases and built tools that drive impact at companies like Caviar, DoorDash and Mudflap. My fascination with what makes great products and teams thrive has fueled this side project: Strome.

Why Strome?

Engineering teams often face three key challenges:

  1. Unclear Progress Visibility: Projects stall or veer off course without early detection.
  2. Inconsistent Delivery: Delivering value consistently is hard, especially in fast-moving environments.
  3. Lack of Predictive Insights: Teams rarely know when work will be done with confidence.

These challenges slow down innovation and frustrate teams striving to ship work that matters. I’ve seen firsthand how vital it is to keep teams aligned, efficient, and motivated. Strome is my attempt to address these pervasive problems.

What is Strome?

Using Strome is like having a bird's eye view of your engineering team and a trusty co-pilot. It brings together all of the data from the tools you use like Linear, JIRA, GitHub, and more. Analyzes changes in real-time and provides updates to you and your team to keep projects on track.

Why It’s Different:

  • Modern-approach: It's designed to be fast and easy to use.
  • Developer-friendly: Strome is equally a tool for the developers as it is for the managers.
  • Collaborative: Central to Strome's approach is collaboration.

Goals

Short-Term:

  • Launch a robust MVP with Linear integration.
  • Deliver daily and weekly updates to users that are concise, actionable, and insightful.

Long-Term:

  • Expand to support other popular issue trackers and source control tools.
  • Become the go-to tool for engineering managers who want clarity and predictability in project delivery.
  • Build a vibrant community around data-driven engineering leadership.

Why Build in Public?

I’m building Strome in public to share the journey, gather feedback, and stay accountable. Transparency helps me create a better product while fostering a community of like-minded people who care about engineering excellence. Building in public also invites valuable insights, ensuring Strome solves real problems for real teams.

I'm also looking forward to share some of the techniques and learnings with the IH community.

What You’ll See in Upcoming Posts

Expect regular updates on:
• Development progress: Milestones hit, challenges faced, and lessons learned.
• Behind-the-scenes decisions: Insights into product, design, and technical choices.
• Community involvement: Opportunities to shape Strome’s roadmap through feedback and suggestions.

💡 How You Can Get Involved

I’d love for you to join me on this journey! Here’s how:
• Follow along: https://strome.app/blog
• Subscribe: https://strome.app/newsletter for exclusive updates.
• Give feedback: Share your thoughts on what features or improvements would help your team most.

I’m excited to embark on this journey and can’t wait to see how Strome evolves with your support. Thank you for your interest—I look forward to learning together as we build something impactful.

Stay tuned for the next update, and feel free to reach out with any thoughts or questions!

posted to Icon for group Building in Public
Building in Public
on December 1, 2024
Trending on Indie Hackers
I'm a lawyer who launched an AI contract tool on Product Hunt today — here's what building it as a non-technical founder actually felt like User Avatar 142 comments “This contract looked normal - but could cost millions” User Avatar 54 comments A simple way to keep AI automations from making bad decisions User Avatar 52 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 41 comments Never hire an SEO Agency for your Saas Startup User Avatar 40 comments The indie maker's dilemma: 2 months in, 700 downloads, and I'm stuck User Avatar 40 comments