As an organization scales and grows, the layers through which decision making is required inevitable increase. Now, that doesn't mean you have to accept this. You have found yourself in an opportune place where you can have impact and reduce some of the overhead. BUT, be warned, you can never fully eliminate overhead. That is the cost of growth and BigCo status.

One of the interesting challenges for engineering teams is dealing with the vast amount of artifacts (meeting minutes, design docs, engineering 6pagers, reference docs etc) that get created. Here is one way to manage that information flow.

Native Zapier for your SaaS!

- Give users integrations that are beautiful with uncompromising functionality. - Create Integration Wizard, embed them in app, or roll out an entire marketplace. - No-code tools to build any workflow and low-code tools to scale and connect to any app.

Just launched on PH -> https://www.producthunt.com/posts/integry

Just launched on Produ

My biggest bone is exactly as you point out, how quickly or how large is our bug pile never reflects the end outcome. Numbers can be skewed and the really smart leaders dig deeper and only use the numbers as a indicator never the diagnoses. Your tool looks freaking interesting. Really cool.

Thanks! Try it out and let us know what you think. It's free to use up until you've created 250 work items (which takes most teams a while). We love having chats with teams that try it out, both to know what would make it work better for them, but also just to talk through how they work today and see if we can help them reach their aspirations for how they want to collaborate as a team.

This is such a great way to keep the sword sharpened. I am really excited to see and quite inspiring that the author even embarked on this mission.

I’m on a quest to learn Figma in and out and for me building things I need or want to use helps me learn better. So, here is an enhanced PERT chart file that you can duplicate and try out in Figma yourself. It’s a work in progress, great for visual presentation, slide decks, or plain mapping out requirements. Love feedback and I plan to continue to add more and eventually make my way to a plug-in. Enjoy.

best analogy ever. What is more important to you?

Effectiveness. Being efficient is only helpful if you are effective.

If the room still smells like shit after all that shoveling, does it matter how fast you shoveled?

Indeeeed!

I have toyed with providing a confidence indicator with each date but % or these average numbers are rife for interpretation. What has worked for me is highlight the eta then state the hard facts - these dates are based on the following assumptions and here are the potential risks that will push these dates out. But as codingdave says, you choose when to deliver or what we deliver - basic constraint theory (cost, scope, time)

I am focusing more on building things with tools I have never used before. Constantly retrospecting my choices in professional and personal life to find ways to do things better. Also the usual - reading books, blogs, following better and smarter people on Twitter. I avoid LinkedIn... it's just an echo chamber on high-fives now.