 |
| [image credit: Guren-The-Thirdeye on pixabay.com] |
Today's meditation:
Today I read a LinkedIn post by a Meta IT
leader...with a long list of technology preferences/choices by which
they would identify when NOT to hire someone...they also included design
and architecture reviews.
To me, that is a very harmful belief. It smells of hubris. It is toxic.
I would hope that is not a commonly shared belief within Meta...but if it is, it would explain much.
No one person knows everything.
Humility is a valuable character trait in every leader.
Assuming you probably missed something should be a First Principle for any practice of design or architecture review.
Even if the design and architecture are correct - you may still yet learn something by engaging in a review with others.
But,
here's the point that most people miss: Design and architecture reviews
are also teaching and communication tools - for the benefit of others.
In
40 years, based on my many and varied field observations, across many
organizations, for countless projects and initiatives - for almost any
non-trivial problem, I think there have always been some useful
observations, questions, suggestions, concerns raised - during a design
or architecture review. In some, catastrophically bad decisions were
corrected.
You
do not waste time by engaging in design or architecture reviews - you
are performing an important and necessary governance function - to
mitigate potential risks, as well as supporting the communication (and
awareness) aspects of change management.
No comments:
Post a Comment