3 ms·
> You should have product and design teams that tease out user problems and come up with solutions. If the solutions are technical, it makes no sense whatsoeve
by erichocean 10y ago
> You should have product and design teams that tease out user problems and come up with solutions.
If the solutions are technical, it makes no sense whatsoever not to include the tech team in the solutions.
I can't tell you how many times I've been given a "solution" that was needlessly complex at the technical level because the product team thought it was "easy" and were "helping" the tech team out. Product people often have no idea which approaches make sense technically, and worse, apparently no intuition about tech. It's amazing, really.
- vcarl 10y agoIt definitely makes sense to have a technical person sit in on later stage product discussions to point out when minor tweaks will have significant impact on the implementation, but there are discussions that don't need technical input. IMO technical people should be brought in when making a wireframe or some other "handoff" from product/design to implementation.
- slavik81 10y agoThe domain specialists know what their customers would like and are thus fantastic at evaluating proposals, but they don't know the range of possible solutions nearly as well as the people doing the implementation. Someone technical can propose something that the design side never considered because they didn't know it was even possible. Having people from the technical side in there early also means helps to spread understanding of why something is designed as it is.