Standardized reporting is an intricate type of reporting process that aims to produce consistent, reliable, actionable information from disparate systems or sources. A reporting process is standardized if it can be applied across different business units or sub-units in an organization. The processes that generate and collect the data to be reported on must remain the same across all the business units.
For an organization to understand the status of conditions in real time, and make decisions quickly, standardized reporting is required. A universal understanding of information enables clarity and transparency. Clarity supports effective communication based on trust. And studies show that effective communication leads to enhanced productivity and deeper customer relationships (Source).
It’s not a stretch to say that data consistency creates a competitive advantage over other organizations that do not have standardized reporting processes.
Even if you’re not a superstitious person, it’s likely at one
point in your lifetime you knocked on wood in an attempt to appease the gods of
fate. Or maybe you made sure to close up that umbrella before stepping into
your house. A couple seconds to rap on wood here, a few seconds of standing in
the rain there—minor inconveniences to soothe away the universe’s impending
spells of bad juju.
The reality is that no, wood is not magical. And opening an umbrella indoors doesn’t shepherd evil ghouls into your home. These quirky habits
don’t add tangible value to our lives.
However, superstitions like these aren’t made up out of nowhere. They often arise from practical behaviors which may have made sense at one point, but lost their fundamental meaning after passing through generations. (Are umbrellas indoors really bad luck? Or did someone long ago get a bad poke in the eye?)
These learned behaviors take root over time, through
generations of practice and habitual routine. They reassure people that no
unintended consequences will come their way if they unquestioningly perform
things a certain way—the way they’ve
always been done.
Similarly, superstitious behaviors are alive and well in your
organization. IT superstitions aren’t supernatural but rather the culmination
of each user’s quirks, a natural evolution of processes, systems left
unchecked, and a game-of-telephone effect.
As with most significant changes, digital transformation can elicit both passive and aggressive reactions. In the correct context and with the right audience, both perspectives can be valid and useful. How can IT leaders embrace these representations to enact true transformation within an organization? (more…)
“Culture eats strategy for breakfast,” is a famous quotation attributed to the late business management guru Peter Drucker. While a debate continues as to whether Mr. Drucker actually said it, the statement itself merits further exploration. I believe it means that any great strategy regardless of the depth of research, hard work, number of paid consultants, and even its own brilliance, will not achieve its intended future state if it fails to take an organization’s culture into consideration.
For part three in my Agile journey series, I will examine the importance of addressing cultural elements to achieve a successful Agile transformation. (more…)
While IT implementation challenges may seem similar across industries, it often takes a deeper dive into a profession’s nuances and specific constraints to fully understand potential barriers to success. I was reminded of this recently at home during dinner. (more…)
The promise of Agile is speed to market for delivering incremental value to the customer, but why is the adoption of Agile in organizations so difficult and slow? As addressed in my recent blog post, “Are you Using, Doing, or Being Agile?” Agile adoption takes more than just checking boxes, but rather is a complex, multi-phase journey. And any unfamiliar journey requires the navigator to know the destination. Have you tried using GPS without entering an address? Understanding where you are headed is a key component of any successful endeavor. (more…)
An Agile transformation is a journey. A journey has many ups and downs, and an Agile journey is no different. Another way of thinking about this is how a company can reach Agile maturity. Just like playing an instrument or participating in a sport, practice makes perfect. However, that is not the full story.
Today, headlines about digital transformation dominate blogs and journals. IT leaders feel that they should have already started their organization’s transition into the digital age. But the amount of buzz around this trend shouldn’t force you into a hasty decision.
For years you’ve been told to avoid technology for technology’s sake – yet the same trap is catching CIOs pushing for digital transformation because everyone else is doing it. Like any IT initiative, digital transformation only makes sense if it supports your organization’s overall strategy.
A Center of Excellence—such as an OSM (Office of Strategy Management), PMO (Project Management Office), IT Governance, Continuous Improvement, or similar task force—is usually established to achieve one or more of the following core objectives within an organization:
- Implement and popularize a best practice
- Add a new capability, function, or technology
- Improve utilization of (or return on) an asset
- Upgrade employees’ skillsets
Download this Executive Field Guide as a .pdf
Leadership requires taking risks. But technology must work reliably. How do IT leaders square these two realities?
CIOs are driving organizational strategies now more than ever. The more a CIO’s success is tied to business outcomes, the more risk they assume. Traditionally, CIOs have been responsible for KPIs like uptime and system availability to support internal productivity and operational efficiency. But suddenly—now that all industries are becoming digital—there is much more at stake.