News for hackers. Stuff that matters.
Re:Ask HN: How do you divide time between engaging with user... by bsldld on Thursday June 18, 2020 @02:39AM (#23560405)
>> Do you know what to do?

> No: Engage users

> Yes: Build

So the task are sequential? I was trying to understand how to best do this parallelly.

Re:Ask HN: How do you divide time between engaging with user... by werbel on Thursday June 18, 2020 @06:08AM (#23561615)
This is what I consider to be a "plan":

> Problem definition > Product solution > Technical solution > Task breakdown > (optionally: > Estimation > Timeline)

Of course there's always some feedback loop between items in the sequence but for given scope it's a good idea to minimize it.

Or in other words: Pick a scope/feature/project, let's say proof of concept for your initiative. It seems like your problem description is robust enough so let's skip to Product solution.

It's a good investment to define everything you can define before stating actual implementation. If you still have some questions to answer then get the answers if that's possible. People have the tendency to leave the "unimportant" details for later but there's no gain in that. You have to spend the time sooner or later anyway. Better to do it sooner because sometimes the "unimportant" detail forces you to go back and rework bigger part of your solution.

Have your entities defined, user stories, UX mock-ups ready before working on technical solution.

Have a technical solution described and validated before you start implementation.

This way you mitigate the risk of being forced to go back to previous steps wasting time or being stuck with sub-optimal solutions.

So regarding the parent comment. If you know enough from the users/market research/cogitating to be reasonably sure about the next step then execute it. Once you get there it's time to continue the research with what you already have in mind.

Otherwise you risk getting stuck in an endless loop of tweaking and changing decisions without reaching tangible milestones.

Re:Ask HN: How do you divide time between engaging with user... by muzani on Sunday June 21, 2020 @07:22AM (#23591379)
It's a loop. You can loop it as frequently as you like. A big company might do this once a month, a true startup would do it every few hours.

It can be parallel if it's multithreaded. Certainly you don't expect one person to build and engage simultaneously, but quite often there is a list of think you know but aren't certain, and the product team can still engage users on those uncertain parts.

Re:Ask HN: How do you divide time between engaging with user... by AlchemistCamp on Thursday June 18, 2020 @06:14AM (#23561644)
Humans are bad at doing things in parallel.
Re:Ask HN: How do you divide time between engaging with user... by galoisgirl on Thursday June 18, 2020 @06:47AM (#23561828)
There is no true parallel. It's small chunks of time, separated by interruptions and context stwiches, and interruptions and context stwiches are expensive.
Re:Ask HN: How do you divide time between engaging with user... by aloisdg on Thursday June 18, 2020 @06:00AM (#23561582)
Build in open source.