Style is an expression of the interest you take in the making of every sentence.
It emerges, almost without intent, from your engagement with each sentence.
It's the discoveries you make in the making of the prose itself.
Where ambiguity rules, there is no "style"—or anything else worth having.
Pursue clarity instead.
In the pursuit of clarity, style reveals itself.
I have seen autistic children drawing at a terrific speed and I've always thought that my drawings should not be less rapid, because that speed gives them insignificance. In this speed lies their abandonment and it may cause them to be overlooked as mere doodles. However, I understand that they are like that pristine light that appears when they tell you that you have a tumour. In an instant, everything becomes clear and well-defined. All contours are cruelly illuminated as if it was worth taking a final look at the world. At such times, although the lines in the drawings clump into a skein of events that are indecipherable to ordinary mortals, they can be described in detail by the victim one by one. These are moments when weeds regain their nature as plants.
Only now can I understand these drawings as simple moments of clarity.
In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us.
However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap.