•   Article   •   7 mins

How I Learned to Stop Worrying and Love an Agile Work Environment

Career mobility has become an increasingly critical component of a healthy enterprise talent strategy; it’s cheaper than sourcing external talent, and it drives employee engagement and unforeseen innovation. But because it is tied to so many areas of the business — talent acquisition, learning and development, compensation, workforce planning — it’s hard to know where, how, when, or with whom to start.

A global, top-down mobility approach is appealing but increasingly, the complex strategies that solve today’s needs are outdated by the time they’re implemented globally. Organizations notoriously spend years on competency frameworks, for example, only to realize they are outdated by the time they’re complete. These tumultuous conditions, we hope, are temporary. But if COVID-19 has taught us anything, it’s that the pace of change will only accelerate. Rather than ignoring this reality, organizations should build a culture of experimentation by favoring a more agile work environment over long-range planning when innovation is required.

In the early days of software development, the business would put together long, complex lists of technical requirements, and engineering would commit to building a product, exactly as outlined, with every associated bell and whistle. Turnaround times were measured in months or years, with few mechanisms to capture feedback on usability, value, or changes in the market. The products built this way were sometimes successful, of course, but the risks were huge: what if users don’t like this solution? Or can’t use it? What if the problem has changed so dramatically that our solution no longer addresses a need?

These risks pushed IT to move toward agile methodology — building lean first iterations, collecting feedback quickly, and releasing and testing improvements more frequently. This takes the burden off of the initial requirement-gathering phase, acknowledges the dynamic nature of today’s world, and prioritizes the most important type of feedback: the kind we get from users when they’re actually using the product.

People in the L&D space know that stealing from marketing and IT can sometimes garner amazing results — and this is no different. You can steal the idea of an agile methodology as well to create an agile work environment at your organization. Let’s take a look at how this can be done.

1. Champion an agile work environment within your organization.

Usually this requires experimentation. Perhaps you’re ready to roll up your sleeves and get going. You might even feel a little excited. But then you remember: you work in a corporation. Things are complex, sometimes bureaucratic, and principles that work for startups have failed in the past (remember the bean bag chairs?) That’s not how budgets get allocated, and you don’t want to risk being seen as naive.

Luckily, there’s a ton of research to tap into as you become your team’s lean champion. One study found that projects applying lean methodology were more likely to come in under time (5% sooner), where others usually finished right at time. Budget-wise, lean projects came in, on average, 9% under budget, while others were only 2% under.

The impact of a lean approach when creating a more agile work environment

A company Degreed recently worked with had a large call center population, and trouble with turnover. Attrition rates had been raising red flags in this part of the business for years, and engagement rates for this population were low. One of our Degreed champions committed to approaching the problem differently, and began by compiling data on previous efforts. There had been some work done in the area, but many of the solutions felt like shots in the dark. She knew she needed to better understand the problem before she’d find the right solution.

She didn’t begin by championing agile practices across the entire organization all at once. She chose to implement an agile work environment for one particular initiative to demonstrate the power of the approach.

2. Get to know your employees.

Remember when implementing an agile work environment, we’re looking to maximize value for our employees, which means we have to first dig into their challenges. Most enterprises begin with engagement surveys, and these are great places to start. Many of our clients, for example, come to us with a goal of improving the learning experience after a less-than-stellar result for a question like “How does the firm support your development?” While investments in Learning Experience Platforms are great ways to enable your team to drive more meaningful experiences, creating real value for employees requires going deeper into their challenges with the current environment.

Whether it’s in response to an engagement survey, or retention/promotion rates within an area of the business or demographic, grab a few of these folks (and a few of their managers) and speak to them candidly about what’s going on. Interviews work best here, but a follow-up survey with free response can work well too, depending on resourcing. In some cases, especially if there’s a lack of trust, it’s helpful to use a third-party firm, but even in high-trust environments, ensure your employees know the responses are confidential. Everyone has to be aware that this isn’t a shame or blame game.

Conducting interviews to deeply understand the challenges your people are facing takes discipline. This framework from the Silicon Valley Product Group has been helpful as we’ve prepared for and conducted interviews like these.

Our call center champion found that many people were leaving within the first 90 days, and those that made it past 90 days were likely to leave at around two years. So her problem was actually two problems, and she used her interviews to dig into each. Because of the high volume of hiring and the high turnover, she was able to sit in on exit interviews for both populations. 

3. Define employee challenges. These are the problems you’re trying to solve.

Once you’ve conducted the interviews, it’s time to make sense of what you learned. Are you hearing similar themes from your employees? If so, what are they? (If not, you likely haven’t spoken to enough people yet, so get back out there!) Group what you’ve heard into the key challenges and prioritize. 

When prioritizing, you’re living in the tension between two poles: maximizing user value and minimizing waste. At this stage, imagine Steve Jobs on your right shoulder and Marie Kondo on your left. Steve says think bigger, and focus more on delight. Marie helps to keep unnecessary complexity in check. If talking to imaginary characters doesn’t work for you, try using the Value vs. Complexity model to rank these problems, with the goal of finding those with the highest potential value and the lowest effort required to solve.

Find the problems with the highest potential value with the lowest effort required to solve.

In the call center, it was discovered that employees leaving within 90 days of being hired struggled with many things, chief of which was friction in processes and social isolation, whereas longer tenure employees were leaving largely due to lack of career progression. Managers were stretched so thin that they could often not give either population what they needed: adequate onboarding or adequate career conversations.

4. Design a Minimum Viable Product (MVP).

Once we have a clear understanding of our priority problems, we can start to form hypotheses about the best ways to solve them. The critical element in an agile work environment is that our solutions, no matter how sexy they seem, are hypotheses. For each problem, frame your solution as an MVP, identifying:

  • Value proposition: how will this solution create value? How will it solve the problem we identified?
  • Key activities: what do we need to do, at a minimum, to drive this value?
  • Key resources: what will we need to execute on the above? 
  • Metrics: how will we know if it succeeds?

In the call center, one elegant solution was proposed: give longer-tenured employees opportunities to mentor new employees. The hypothesis was that this would create engagement for each population, and could provide career development for the tenured folks. A program was defined, and success would be measured based on a pre- and post-engagement survey, as well as retention rates for the participating population.

Framing a solution as an MVP for a more agile work environment

Remember, the first iterations of program rollouts are about maximizing value, but they’re also about learning as much as we can, as quickly as possible, and about whether our solutions are the right ones. So as you’re designing, keep in mind that MVPs may require more manual effort than you’d hope. This is fine because if it works, you can invest more in infrastructure later. With reducing waste as one of our guiding principles, we can’t invest more than necessary in a solution we don’t yet know will work.

Depending on the number of problems you’ve prioritized, you may need more than one MVP. Depending on your resourcing and other constraints, you can run these MVPs in parallel or sequentially. One thing to note: if you’re working to tackle multiple problems for the same user group, you likely want to run these MVPs at different times, so you can measure results from each independently.

5. Measure & iterate.

Once you’ve rolled out your MVP(s) and collected your results, it’s time to make decisions about what about this solution, if anything, drove value as measured by our metrics. This is the time where we may want to think about how to more efficiently scale, make some tweaks and run another MVP, or scrap the project altogether. This is the process that will dictate organizational agility

In the call center, the program reduced turnover for the new employee population but did not have a meaningful impact on the tenured employees. Before scaling the mentorship program, our champion will conduct another set of interviews to understand the pain points for the longer-tenured folks. She solved part of the problem, but needs to iterate in the next go-around to drive even more value.

So if the MVP is a “failure” — i.e. it didn’t drive the results you were hoping it would — it’s time to celebrate! You learned something valuable, and because we rolled it out as an MVP, we wasted as few resources as possible. This is probably the most important element of embracing an agile work environment: we have to have the humility, honesty, and confidence to pivot entirely when something isn’t working. This will lead to incredibly impactful results in the end.

Want to learn more about creating an agile work environment? Take our mini-course on career mobility — five days, five experts, 15 minutes per day. Sign up here!

5 Days of Career Mobility

More Articles in Career Growth

Let’s keep in touch.

Sign me up for the monthly newsletter with exclusive insights, upcoming events, and updates on Degreed solutions.

Your privacy is important to us. You can change your email preferences or unsubscribe at any time. We will only use the information you have provided to send you Degreed communications according to your preferences. View the Degreed Privacy Statement for more details.