Uncategorized

Thank you for checking out Part 3 of our Evolution of Modern Work series. If you’re not caught up, check out Part 1  and Part 2. In these two parts, we introduced the pre-Digital Revolution concept of work and how it fundamentally transformed with the introduction of technology. We then explored the two phases of Enterprise Work Management that aimed to address the challenges of modern work but didn’t quite get us there.

Modern Work, Mastered

Today, we’ll see how the adoption of best of breed systems was a significant first step in addressing the challenges of modern work. But to bring your A-Game, your systems must be paired with Intelligent Integrations, and something called an Operational System of Record.

Intelligent Integrations

If we think back to what organizations were trying to accomplish with big-box systems and custom development – “a common frame of reference for work across the organization.” – It becomes evident that disconnected best of breeds don’t make the cut.

It is not by chance, then, that incredibly agile integration technologies are flourishing in the best of breed era. There are four best practices, depending on the integration scenario:

1. Application Program Interfaces (APIs): An API is a connection between two systems for very specific purposes (e.g., pulling a Customer ID from System A for use in System B). Out-of-the-box APIs are incredibly common in nearly all SaaS. Particularly in best of breed systems so that they can “talk” to other systems to create a more seamless user experience across platforms.

2. Integration Platform As A Service (iPaaS): iPaaS is identical to APIs in purpose and outcome, but they offer extreme, codeless agility in connecting any Cloud-based systems – whether they have existing APIs or not.

3. Custom Integrations: Custom integrations remain an option, particularly in complex integrations or when integration involves any system that is not Cloud-based – some on-premise and legacy systems.

4. Robotics Process Automation (RPA): RPA is an appropriate option when the integration involves automating a highly repeatable process that occurs frequently and requires human interaction.

But let’s return to the example from APIs. Let’s say that the Customer ID pulled from System A for use in System B is then used by an Analyst to do a lookup on a public website. If she is performing 500 Customer ID searches a day, this is an excellent use case for RPA – automating the process and opening up the Analyst’s time for higher-value work.

But merely connecting the best of breed systems is not enough. In the same way that the human body operates through a complex neural network and all governed from a central command – our integrated best of breed network must also be connected and governed from a central command.

Operational System of Record

Every major asset of an organization has a dedicated system of record to administer, track, and manage the asset: human resource management systems for employees, customer relationship management systems for prospects and customers, financial management systems for money and transactions, contracts management systems for contracts, and so on. But what about work?

Work as an Asset

If we recall the characterization of work in the modern workplace, it’s the shepherding of information from one place to another. Information as an asset is not a new concept. The likes of Gartner and even the current US Federal Government Administration have laid out strategies for leveraging data as a strategic asset and championed the resurrection of the Chief Data Officer (CDO) role.

Another compelling case for work as an asset come from Harvard Business Review. They note that small ideas, borne at the proverbial water cooler, often make their way into business processes. And over time, more and more of these small ideas create a sort of intangible intellectual property – one that wouldn’t be showcased in a product or service or documented in a patent. These ideas become powerful differentiators that are extremely difficult for competitors to replicate.

Work is an invaluable asset on-par in value with, if not greater than, all other corporate assets. Institutional investors, who make investments based on hard, tangible, qualitative measures are looking at softer, more intangible measures because of a rather shocking discovery: “The most valuable aspects of jobs are now, ‘the most essentially human tasks: Sensing, judging, creating, and building relationships.’ A great deal of a company’s value now lies ‘between the ears of its employees.’ And this means that when someone leaves a company, he takes his value with him – more often than not, straight to the competition.”

Work Management “Systems”

Whether we acknowledge work as an asset or not, we are tracking it. Both structured work (e.g., planned project tasks) and unstructured work (e.g., an instant message conversation) are both tracked in systems, in documents, and our heads. We’ve even connected many of these tracking mechanisms through the integration methods described above. But connecting the dots still hasn’t revealed the big picture: Are the right people enabled by the right tools? And are they working on the right things, at the right time in the right way to achieve the right business outcomes?

Operational System of Record

The Operational System of Record (OSR) is the central command of our work neural network, the dedicated system of record for work. Work itself may be carried out in the connected best of breed systems. The OSR’s role is to create a virtuous circle, where tightly aligned strategy, operations, and tactics are planned, executed, measured, and adjusted in the context of enterprise business outcomes. The OSR achieves the organizational alignment of the Good Ole Days while capitalizing on the very best technology has to offer.

 

Stay tuned for Part 4 of our Evolution of Modern Work series. In Part 4, we’ll delve into why mastering modern work is incredibly important. Additionally, I’ll introduce you to some of the organizations that are at the top of their game – the A-Game – in mastering modern work.

 

Unlike the traditional or “waterfall” method of software development, the agile approach does not treat analysis, design, coding, and testing as discrete phases in a development project. Agile has quickly become the standard methodology as businesses see the many advantages of adopting a more flexible approach to software development.

With testing integrated into the development process from day one, agile development often leads to higher quality products, as well as reducing risk. However, making the switch from waterfall to agile can be tricky. Many development teams end up awkwardly straddling the fence between the two approaches, which can make it difficult to effectively manage resources.

To root out any bad habits that carried over when your development team made the switch from waterfall to agile, look out for these warning signs that your team isn’t as agile as you think.

1. No sprint retrospectives

sprint retrospective is a meeting that occurs after a one-month development sprint. Usually held once a month, this is an opportunity for teams to discuss what worked well in the sprint, what could be improved, and what the team will commit to doing differently in the next sprint.

If your team does not hold sprint retrospectives, you are missing out on a valuable opportunity to change work processes in order to improve the quality of the end product. Holding no sprint retrospectives means that problems persist throughout the development process, exposing your business to the risks of waterfall methodology.

2. Long stand-up meetings

Many people resist adopting agile methodology because they think they will spend too much time in meetings. While it’s true that agile development involves a daily stand-up meeting, these should be kept short to avoid eating into everyone’s work time. In fact, the name stand-up comes from the idea that people should literally stand during these meetings so they have an incentive not to let them drag on too long. To avoid stand-up meetings overrunning, have someone with good facilitation skills lead the meeting.

3. Improper product backlog management

product backlog is a list of all the work that needs to be done for a particular product, ordered to prioritize the most important tasks. Sometimes, backlogs can become so large they are difficult to work with. In that case, you need to break the backlog down into short-term and long-term items to make it easier to manage.

4. Failure to deliver product increments after each sprint

One of the principles of agile is that working software is the primary measure of progress. If your team does not deliver a product increment after each spring, that is a warning sign that you are slipping back into waterfall methodology.

5. Urgent tasks that interrupt workflow

When you use the agile approach, your workflows should be regularly adapted to prioritize the most important tasks. If urgent tasks frequently come up and throw your workflow into disarray, that is a sign that the team hasn’t done enough planning to anticipate the upcoming demands of the project. This might be because they are hanging onto waterfall ways of working, such as setting out a roadmap at the beginning of the project and failing to reassess it often enough during sprint retrospectives and daily stand-ups.

We’re proud to announce that Kevin Ellington is joining the LeapPoint leadership team as a director in our People & Change group. Kevin will serve as our Center of Excellence practice lead which is focused on enabling our enterprise clients to facilitate user adaptation and learning, and gain efficiencies through the reuse of capabilities and resources. He will also lead LeapPoint’s internal CoE, supporting our commitment to operational efficiency and continual improvement.

Kevin earned his Ph.D. in Organizational Leadership from Regent University and has leveraged his learning to benefit executives and their companies for over 25 years. Most recently he’s dedicated his time to helping companies deploy Centers of Excellence and drive the success of enterprise initiatives. Kevin connects quickly with clients, understands their needs, and equips teams with the knowledge, skills, and tools needed to achieve both quick wins and long-term strategic objectives.  He has taught leadership both nationally and internationally and we’re incredibly excited for him to bring his skill, passion, and expertise to helping us drive enterprise change for our clients.