Personally, I like the idea of "3 strikes" If a task occurs 3 times, everyone should ask themselves "can we automate this?" Worst case, it leads to a more streamlined process, even if we can't automate it 100%.
This randomly crossed my mind while working today.
Obviously, this probably depends a lot on the size of the design and development teams and how they work together.
And of course, the more organized a Figma file is before handoff, the better. Flows, states, edge cases, notes all of that makes things easier for developers.
But getting everything perfectly organized takes a fair amount of design time too.
After more than three years of observing this platform (mainly in the forums), I can see which posts have helped you the most. [Yes, I can tell based on their performance.] In addition to updated news from the tech industry, you liked the most:
website roasting and
tagline adjustments/improvements for launch day (mostly from @aaronoleary )
The most valuable thing you own in the AI age isn't your AI. In my opinion, It's your data model. My 2nd vote would be Sales!
I've been building business software for the last year, and I keep watching companies make the same expensive mistake. They add an AI tool for support. Another for writing. Something for invoices. A notetaker. Each one is genuinely good at its job.
And each one is a silo.
Six months later somebody asks a simple question "what did we actually sell this month, and which of it got collected?" and there's no answer. Not because the data doesn't exist. Because it exists in eight places, in eight shapes, and nothing reconciles.
I've been heads-down building for the last few months, and now that I'm past my first launch I'm hitting the classic problem: every hour spent writing code is an hour not spent talking to users, posting, or actually finding people who need what I built. For those of you doing this solo (or with a tiny team) what's your actual split? Is it a strict schedule (mornings = build, afternoons = marketing), or more reactive depending on what's on fire that week? Has that ratio shifted as you've grown, or gotten more lopsided one way?
Trying to figure out if I should be spending less time in the editor right now, or if that's premature.
My team and I are in an exciting position we ve built a pipeline of multiple products that we plan to roll out one by one over the coming months.
Before we start launching them officially, our goal is to build a solid base of early followers, waitlists, and subscribers for each product so we can hit the ground running on day one.
For those who have successfully launched multiple products or built strong pre-launch momentum:
I want to launch the product faster, and for me, functionality matters more than aesthetics. But my designer keeps saying aesthetics is subjective. There are a lot of things that could hold us back from an early launch. How I should manage it? Does Aethetics such subjective for early launches?
