From process-less
to process-light
aka how to scale our Product Development and keep Surfer Spirit
Things we do right
Always thinking what's the 80/20 essence
Having flexibility about our priorities
No
micromanagement
Problems
we face
Unpredictable delivery
"when is this going to be shipped?"
Context switching
"just help me with this small thing"
Unclear expectations
"is this a part of the scope?"
Huge catch-all features
CE 2.0 taking a few months to complete
Onboarding new team members
"what's the process for developing new features?"
The gist
Timeboxing
asking "what can we done in two weeks" instead of "how long will this take"
Shaping
try to understand and explain problem really well
sketch out the proposed solution
at the right abstraction level (not too detailed)
<show_example_pitch.exe>
always think what's MVP and what's optional
Betting
"what's next up to work on?"
detailed plan 6 weeks ahead, then reiterate
great ideas stick without having to track them
Building
super-small teams for the most efficient communication
"let them do the job" attitude
team should manage their time so that at least something is improved upon the time to ship the work
laser-focus on delivery with as little distractions as possible
It's all very similar to what we already had
Unknowns
Will we like working this way?
How to do support?
Is Surfer transforming into Basecamp?
Time for Q&A
Moving on from process-less product development
By Lucjan Suski
