zlacker

>>femfos+(OP)
> I’m not going to suggest a solution to the problem of men clamming up.

I find this a little frustrating, they’ve noticed a pattern of behaviour that concerns them in an area they are clearly invested in - yet they have no thoughts or suggestions on how to address this? Is it possible they are not offering such thoughts because of the same issue they have highlighted in the article?

>>simonb+ea
Why does someone need to have a solution in order for their observation of a problem to be considered valid?

Maybe the problem is real but they just don’t have as solution?

>>zepto+Eb
But they have no thoughts on a solution at all? Nothing? Not even an inkling of a suggestion to continue the discussion?

>>simonb+Qb
It's often useful to split up a solution between defining the requirements in one doc, and the design in a separate one. If you bleed design ideas into the requirements, you can get tunnel vision