I've watched analysts send a link to a query or dashboard and call the job done. Sending the link is what the work looks like when the job was defined as produce the artifact, not change the decision.
One push. You put the hard part in the interpretation and frame the fix as a habit. But forming the opinion was never the hard part. Having the authority to act on it is. People stay in the Data layer because the org chart said build pipelines. It never said walk into the room and size the opportunity. Authority is relational, not structural, and most analysts were never granted it.
Define ownership first, or the habit has nowhere to land.
Strong piece. The no-data-alone rule is going in my practice.
Thanks for this post! I wonder why “Building perspective as a habit” is so often overlooked by engineers like myself— maybe because it feels subjective, difficult to measure, and counter to what drew us to engineering roles in the first place. The unfortunate reality is that we’ll never be able to produce 100% accurate and verifiable interpretations, but there’s still significant improvements we can make by deliberately providing our perspective over just sharing out reporting.
I've watched analysts send a link to a query or dashboard and call the job done. Sending the link is what the work looks like when the job was defined as produce the artifact, not change the decision.
One push. You put the hard part in the interpretation and frame the fix as a habit. But forming the opinion was never the hard part. Having the authority to act on it is. People stay in the Data layer because the org chart said build pipelines. It never said walk into the room and size the opportunity. Authority is relational, not structural, and most analysts were never granted it.
Define ownership first, or the habit has nowhere to land.
Strong piece. The no-data-alone rule is going in my practice.
What an amazing post!
I nodded along every single sentence.
Congrats and thanks Goutham
Thanks for this post! I wonder why “Building perspective as a habit” is so often overlooked by engineers like myself— maybe because it feels subjective, difficult to measure, and counter to what drew us to engineering roles in the first place. The unfortunate reality is that we’ll never be able to produce 100% accurate and verifiable interpretations, but there’s still significant improvements we can make by deliberately providing our perspective over just sharing out reporting.
values > aptitude > skills.