Presenting your data should spark questions or proposals or agreement regardless how much time you put into it.
I agreed with the first 4 points, but the last one seemed weak.
Presenting your data should spark questions or proposals or agreement regardless how much time you put into it.
I agreed with the first 4 points, but the last one seemed weak.
I find that asking one's self this question is helpful : "Are the barriers to believe for concept ________ technical or something else?"
If the answer is that there aren't deep technical barriers - its a good time to stop and start collecting feedback.
Instead of spending time trying to come up with the perfect idea, I work on finding the best way to test many half baked ideas.
Step back and take a look at that statement again.
If you put too little time into it, it'll spark questions - about you, and your process, and the lack of completeness.
If you put too much time in, it'll also spark questions about your productivity; or it will overwhelm the audience and put them into that sort of compliant/bored state where they somewhat shut down and don't engage.
There's an art to answering just enough potential questions while leaving room for people to feel like they're contributing, which builds engagement and really helps turn bored listeners into real stakeholders.
"Perfection is Achieved Not When There Is Nothing More to Add, But When There Is Nothing Left to Take Away"
"Perfection is the enemy of good"
which in the context here relates to smart people wanting to overdo or over-complicate things restated as
"premature optimization is the root of all evil"
recognizing simply that it is possible, easy, and more frequent for smart people to do worse solving problems by trying too hard to do better.