69 products left, but today Beau

Hi friend 👋,

Just a week ago, one of my coworkers forwarded me an article emphasizing the importance of principles above processes. "It all makes sense," he remarked, "but I'm not sure what the writer means when he says principles should take precedence over processes." It's difficult to absorb when you plan your day around well-defined processes. However, after spending so much time on various methods, you understand that the principle, not the process, is what is important. This is why I dislike Scrum and the changes it has made to the product development culture. Consider all of the continuous and repetitive meetings you've had; in most cases, I've found that repetition kills authenticity. If the culture incentivizes the process by talking about how to do it and when to do it, you will eventually lose sight of why you do it. You'll understand what I meant at the 5th Retrospective Meeting or the 7th Daily Scrum... The principles may be something like:
- We are all on the same team. If one of us fails, we all fail
- Giving feedback is an opportunity for both parties
- We should be proud of what we accomplished
- We should understand the user and why we do what we do
If you and your team can agree on these four principles, then anyone, at any time, can call for a meeting to discuss anything. Demo is not limited to Friday nights, despite what the scrum might have you believe. Are free to present your work to the team anytime you feel ready. To some extent, this is what the "principles above procedures" strategy means to me.

Of course, internal workflows are not the only aspect of our work lives. When a new employee is hired, there should be an onboarding procedure that follows a logical sequence. When you get a new customer, when you raise funds, when you sign a contract with a client, when you create a webinar for your clients, or when you announce a new feature... These are the types of things that require a strong process to maintain quality. Explaining processes is often simpler than communicating principles, especially if you have external stakeholders. I discovered today's product during one of the YC demo days and truly like the concept.

Today, beau is our product.

Beau is a platform that allows you to define workflows and invite all relevant stakeholders. You may configure triggers for all actions and steps to quickly automate them. They have various integrations with the existing tool set, which gives the product a lot of adaptability.

I understand how difficult it might be to buy a product that solves a problem that numerous teams are experiencing or improves their current environment. However, you might simply request a demo to test out the platform. They are YC-backed, and as you can see in the image above, they have a lot of community support on Product Hunt. Their website is also engaging.

We’ll talk again tomorrow.