It’s been difficult for me to reconcile these feedback loops and whole-team involvement with the current online push for asynchronous workflows. In my experience, the developers who want to isolate themselves at home or in their office, pull tickets out of a queue and submit a PR at their leisure were the least likely to succeed at improving the product. The developers who never hesitated to jump into a discussion or meeting with the rest of the team or get involved with the product planning sessions were the ones who moved the product forward the most.
Don’t get me wrong: There’s a time and place for isolated, heads-down work. Frivolous meetings and endless planning sessions must be minimized in favor of action. However, the current online mentality in favor of asynchronous work, minimal real-time in-person interaction, and strict “not my job” separation of developer/product manager roles is swinging the pendulum too far in the other direction, IMO. Everyone, from developers to customers, tends to be happier when they’re all included and active in the decision making processes.
For what it's worth, I've worked with a couple teams that were remote and great at this, so it's not impossible. One was a small startup. The developers had worked together in person for years and were really well bonded. Once they added in some remote pairing, it was fantastic. The other was a Mozilla team where they put a lot of emphasis on close collaboration. Between the two, I have a fair bit of hope.
Maybe one of the silver linings of this mess will be that people are more familiar with screen sharing software after this.
This was freelancing though; I had full freedom to do things my way, which is how I ended up working for two weeks to learn about their problems.
And I still prefer delivering food to working on the software. Thankfully, they're super happy with it and there's not much left to do.
Two screener tricks that I recall:
One is getting in a little market research. Add a few questions that you've been wanting to know anyhow.
The other is including plausible-sounding answers that let you reject liars. For example, we had a grid section that asked, "How often do you use these sites?" One axis was frequency, "several times a day", "daily", a few times a week", etc. The other axis was the name of a bunch of sites, including popular things like Facebook and Amazon. But we'd also make sure to include more obscure things, and a couple of entirely fake ones.
Some years back, I started a company with an excellent product manager, one very focused on actual user impact. One of the first things we did is build a tiny, cheap usability lab; every Tuesday we'd have 4 users in to try things out. We rigged it so engineers could watch the sessions remotely, and for the sessions we didn't watch, he'd share key bits. It was really satisfying to see stuff getting used, what worked, what didn't.
Later, as we grew, we still kept the user tests, but added on a slick system for experiments. All of us were involved in thinking about what to test next, how we could make things better. My cofounder was definitely the best at that, but we all made contributions. We all were engaged. We all paid attention to what we were doing for users.
And it helped that despite being a startup, we were big on automated testing and pair programming. When my mom got sick, I took two weeks off and everybody was fine without me. They carried on releasing a few times a day, trusting in each other and in the safety net we had built for ourselves.
It seems to me that the average development process, which is generally about building whatever people with organizational power want, is emotionally corrosive. It wears us down, because it isn't satisfying on a human level. Which, IMHO, makes it way less efficient.