The Sweet Spot: Overlapping Value for Employer and Employee

Definition

The "sweet spot" is the overlap in a Venn diagram where agile working arrangements create value for both employer and employee. Most agile practices can be configured along a spectrum: benefits can accrue entirely to employees (the organization is indifferent), entirely to the organization (employees are indifferent), or to both. The AFF's core insight is that most organizations have overlooked the third option, where mutual benefit is possible and often substantial.

In the Book

The AFF uses Diagram 2.2 to illustrate the concept: two overlapping circles, one labeled "Value for employees," the other "Value for employers." Most traditional flexible working arrangements sit in one circle or the other. Flexible hours and remote work, historically marketed as employee benefits, typically sit in the employee circle alone—the organization tolerates them to retain talent. But the AFF's research found that the same practices, when designed differently, can live in the overlap.

A concrete example: KPMG's Tax Centre of Excellence. The work has seasonal demand—peaks from June through January (tax year end), troughs the rest of the year. KPMG needed to match staffing to demand. Staff wanted flexibility to control their hours. The sweet spot: annualized hours contracts where people work longer during peak months (in blocks of three months) and then have substantial time off during low-demand months, but receive level pay across the year. The organization gets better resource matching and higher productivity; employees get large blocks of free time and income stability. Dominic Casserley (Willis Towers Watson) calls this the defining question for agile working: "You must talk about the benefits for customers, the benefits for talent, and the benefits for shareholders. In the past, the debate has tended to be just talent-focused. I don't think that takes it very far."

Another example from the book: staged retirement. A 57-year-old banker reduced his hours to work Monday–Wednesday, keeping his salary proportionally reduced, so he had a four-day weekend. The organization retained 20+ years of knowledge and mentoring capacity; the employee got to ease into retirement while staying employed. Both sides won.

Why It Matters

The sweet spot reframes the business case. If an arrangement benefits only employees, it competes against other HR costs. If it benefits only the organization, it faces resistance from people asked to work differently without reward. But mutual-benefit arrangements are harder to dismiss—they have advocates on both sides of the organization. This is strategically important: agile working thrives when both leadership and employees are genuinely invested, not when one side is merely tolerating it.

It also prevents the simplistic zero-sum thinking that kills agile initiatives. Many resistance arguments assume someone wins and someone loses: "If you let people work from home, customer service will suffer" or "If we ask people to change shifts, morale will drop." The sweet spot approach rejects the premise: design the arrangement so that the efficiency gain accrues to customers (better service), the autonomy gain accrues to employees (better balance), and the cost savings accrue to the business. When designed this way, resistance evaporates because the proposal isn't a trade—it's a genuine upgrade for everyone.