We define a new product scope for Stacker every week using Linear.
The aim of the process is to deliver all of these enhancements to production before the end of the day on Friday. Here’s the breakdown of Cycle 6 for w/c 13th January 2020.
We kept it the same as Cycle 5: “make leads more likely to subscribe”.
These are the biggest bets in the sprint and we expect them to take several days development time to deliver.
Up until now we have required that the email address of your end user already exists inside your database. …
Dear Stacker –
Right now, despite achieving some complex stuff, our product is actually quite simple. As a team, I think we like products that are simple. Especially ones that are both simple and powerful.
So how do we keep increasing the power of our product, while still keeping complexity down?
Here’s a look at how two of the product we love do this:
We’ve been hearing one phrase a lot from our Stacker onboarding calls recently:
“I want to reduce friction…”
What follows this phrase varies massively depending on what the company does but it always relates to sharing data. For example:
We’ve been blown away how Linear has changed the way we work so quickly, we have ended up dramatically improving our product process empowered by Linear. This post gives a quick rundown of how our new process works.
To keep iterating quickly on our product we are running weekly sprints. Each sprint has a goal which we determine in advance of the week. …
I’d like to drop the the term no-code. I love the movement, but hate the term.
I hate it because it’s always comes hand in hand with its even more ungainly sibling “low code”. Sometimes they’re used interchangeably. And sometimes, they get smushed together as “no/low code”.
I hate it because it has an awkward optional hyphen.
But mainly I hate it because it kinda misses the point. I recently used a product that proudly claims to be “no-code” , but encourages you to create logic via flowchart with so much looping and nesting that it begins to look like…
I love the concept of the format. I’m in. Common wisdom is that starting is hard. I think it’s true but I think finishing is much harder! Let’s try and do both.
I wanted to talk about the different dimensions we need to move our product in. What came out when I started to write it wasn’t what I had in mind at all. I’ll shelve that for another day when the ideas are more fully formed. So bear in mind I reserve the right to redefine product dimensions as something else in a few letters time.
Dear Sam —
We’ve been trying to work out a good format to blog in, and in typical Stacker “meta” style, I think this post is it.
We want to show the world how we think — but we already write down all our best thoughts and ideas, in the form of the “memo” style Notion docs we write. So I propose we start doing these in blog format instead, as letters to each other. I write a post with my freshest thoughts, and you write one back to respond, and give your thoughts. …
I believe that teaching kids to code is not enough for us to become a society where the advances in technology benefit everyone, and that we need better tools to allow everyone — both kids learning now and the people already working — to build the future themselves.
Back in the middle ages, as skills turned to trades turned to professions, it was the deeply skilled practitioners—the artisans—who had all the control over what was produced. The decisions of individual weavers determined what fabrics were produced, blacksmiths what objects were produced. …
Thoughts and ideas from the people who build Stacker…