Projects

Replied to

Karri Saarinen Karri Saarinen

yeah and we do:

1. keep developing the feature behind internal flag, anyone trying it will keep hitting issues

2. bring external beta users

3. keep using internally still

4. do feature roast where internally the whole team tries to be nitpicky as possible and write their feedback

5. release to more users

6. release to all and keep monitoring

7. team doesn't move on for a while even if the project is kind of completed, they will clean up flags, do some other work, while monitoring the feedback coming through from users

The “team doesn’t immediately move on after project completion” part is super important.

You need time to see how it actually lands, learn from real usage, and make those important tweaks while the context is still fresh.

Replied to

Jo-Anne Cruz Jo-Anne Cruz

@ramiroruiz @rosiesherry Hey there Ramiro. Which part are thinking might be time-consuming, building the company or ensuring it's community-led?

I'm a mom too and can relate. It helps that our co-founders are quick to iterate on what works/doesn't. At early stage, "action" is quite slow too

Initiating, I’m by myself in this project and I’m not sure if the time I need to build a solid data base that would be attractive to the community be worth it.

Happy to being proven wrong. But my model doesn’t expect to charge people from the community.

A certain way of improving one’s work is by being in a positions of saying no. That gets you better clients, projects and more time for each one. Easier said than done, I couldn’t afford to say no until this year.

Very excited about this new futuristic project 🤩 all done in #css