Daniel Just
452 posts

Daniel Just
@DanielJustPM
IxD turned Product Manager @dvinciHR, ex-Eurodata, ex-XING

Testing out @HeyGen_Official translation on French and German. I don’t speak either language so let me know if it sounds natural if you do. I hope if you pay you can turn off the color correction. It didn’t work on my phone so I had to upload on my pc. app.heygen.com/guest/template…

In the cut-throat tech world, the few who survive often have one thing in common: They ship incredibly fast ⚡️ Staying ahead in the competitive market is the key to success. But fast shipping doesn't mean rushing products or releasing useless features - it means being agile, flexible, and efficient in product development and release. Startups are known for their rapid growth, and product shipping speed is a key indicator. @paulg, co-founder of Y Combinator, suggests frequently releasing new features can predict startup success. He said: " Mere rate of shipping new features is a surprisingly accurate predictor of startup success. In this domain, at least, slowness is way more likely to be due to inability than prudence. The startups that do things slowly don't do them any better. Just slower. " Why does this matter? Simply put, when you ship quickly, you learn from your customers, iterate quicker, and identify valuable offerings for your users. Let me share 6 simple yet unconventional strategies that can help you deliver value to your users (and you) at the speed of light. 1. Say No to Staging Staging environments, used for testing with simulated data or unreleased interfaces, can sometimes slow down the process. To speed this up, use a feature flag system. This lets you test a specific user experience on a subset of your users in production while still keeping things safe. This way, you're just one click away from going live. This approach means your engineers need to be more responsible, ensuring their features are ready and free from bugs. The trick is to adopt a feature flab system… 2. Adopt a feature flag system A feature flag is a way to flag a specific user experience for only a portion of your users. When you do that, you can learn from production but also be on the safe side. If you want to be the only one to try it out, you can also only flag yourself or your company or your account, which makes it a type of staging environment without the deployment overhead. The great thing about adopting this system is that you are always one click away from going live. Your engineering will now know that when you ship something into the feature flag, it’s only one click away from being released by a Product Manager - usually using very simple no-code interfaces or tools like @LaunchDarkly. 3. QA Straight Away Switching between different tasks (aka context-switching) can slow down engineers. Instead of jumping from one task to another, implement immediate quality assurance (QA). This means checking the work right after it's done. A quick 10-20 minute QA can speed up delivery by solving issues on the spot. While some companies have specific QA roles, many startups find that everyone can participate in QA, creating a culture of shared responsibility and speed. 4. Minimize the Scope A smaller scope allows you to deliver projects faster and more effectively. The key is to dream big but start small. Big ideas are exciting, but they often require a lot of time and resources. By breaking projects into smaller parts and shipping them incrementally, you can accelerate overall delivery. This strategy also allows for immediate user feedback, enabling you to make necessary adjustments quickly. Having a clear scoping phase in your product development process can help you set your initial milestone, collect feedback promptly, and determine the next steps quicker, laying the groundwork for rapid, iterative progress. 5. Be Consistent With Changelogs Changelogs, whether public or internal, are a great tool to help maintain your shipping pace. Regular updates on your team's activities and what you've delivered can foster a sense of urgency and focus, effectively pushing your team to deliver quickly and consistently. By establishing a regular cadence of updates, your team can remain accountable and motivated, knowing that their progress will be documented and communicated. This creates momentum that can significantly speed up your shipping cycle. 6. Define Clear Engineering Ownership Clear ownership of tasks can significantly speed up your delivery. When engineers are responsible for solving a user's problem, they are more invested in the result, which means they’re more motivated to deliver faster. There are fewer delays and bottlenecks because each engineer has a clear understanding of their role and responsibilities. This approach leans more towards an engineering-driven culture, a strategy proven to boost pace in companies like Intercom and Stripe. By empowering engineers to take ownership, you cultivate a culture of accountability and speed. ----- While they may seem unconventional, these five strategies can profoundly improve and speed up your delivery and ultimately drive your product's success. In the fast-paced world of tech startups, speed is of the essence, and these strategies can help you stay ahead of the curve. So, move forward, adopt these techniques, and watch your shipping pace skyrocket. I hope these strategies help you as much as they've helped me and the rest of the June team. Remember, success isn't just about having brilliant ideas; it's about bringing them to life as swiftly and efficiently as possible. If you've discovered other strategies that work well, I'd love to hear about them! DM me 😃 and I’ll share your ideas with the rest of the world.

Introducing DomainsGPT → domainsg.pt Generate brandable & memorable domain names using AI. Powered by @OpenAI and @Vercel Edge Functions ▲

An engineer one lamented to me: “we’ll never fix things, because a PM won’t ever prioritize tech debt over a feature. My response? “You’re right.” 🧵


What are all these scribbles on your keyboard? A brief history of punctuation marks:

A lot of people missed this last week: Canva just announced a suite of new products to challenge Microsoft Office + every other productivity tool. Here’s why I think this might be one of the most significant product announcements ever:





After the last two years of working remotely, I decided to try working in person again. Here are some observations from a week of returning to work: Spoiler alert: In-person work is dead 🧵


