90 entries on engineering, growth, design, and what we've learned building products.
Pretty sites lose to functional ones. An opinionated case for making every design decision defend itself against a metric.
The phrase is overused. Here's the five-test filter we apply to every site we ship.
We do our planning in November and December so January can be a doing month. Here is what we are choosing to focus on and, just as importantly, what we are choosing not to.
We ran a lot of content experiments this year. One of them failed in the way we expected, one succeeded in a way we did not, and one taught us something we probably should have known.
Every engineering decision in Scheduloo is a version of the same question: invest in infrastructure for a future that may not arrive, or move fast for a present that definitely exists.
The things I was confident about when we started are not the things I am confident about now, and what I have learned instead has been more useful.
We ran Diwali campaigns for four clients this year. One exceeded targets, two delivered on expectations, and one was a lesson in why lead time is not negotiable.
We lost the project we pitched for, stayed in contact, and nine months later had a longer and better engagement than the original brief.
After four years of building and maintaining WordPress sites for clients, we have opinions about plugins, and those opinions have saved us from a lot of avoidable problems.
We had assumptions about how Indian mobile users behave on websites. After two years of aggregated client data, we can say which ones were right.
After running paid campaigns for dozens of Indian service businesses, we have a repeatable structure that works more often than it fails.
We have been building Scheduloo alongside client work for over a year. The financial cost is visible. The other cost is harder to name but more damaging.
Showing 1–12 of 90 entries
