liveBook · Manning

Flexibility

As explained in Think Like a Software Engineering Manager

Flexibility is the capacity to adapt arrangements, behavior, or decisions to changing needs and circumstances.

Flexibility means adapting arrangements, behavior, or decisions when needs change. For example, a manager may replace rigid core hours with agreed overlap while allowing people to organize the rest of their schedules around personal obligations and workload. section 3.3.1

Make flexibility practical by:

  • Invite employees to describe conflicts, workload needs, and preferred arrangements before changing policy. section 3.3.1
  • Balance structure with choice by preserving necessary meeting overlap while loosening unnecessarily fixed hours. section 3.3.1
  • Model the behavior as a manager by adjusting your own schedule and remaining accessible outside shared hours. section 3.3.1
  • Support varied needs through work-from-home arrangements, rampback programs, hybrid-work practices, and protected no-meeting time. section 8.4.1
  • Review arrangements through periodic feedback so concerns about tools, processes, support, growth, and leadership surface early. section 8.4.1

A course correction

A manager introduces mandatory core hours to improve communication, then learns that personal obligations and workload patterns make the policy stressful. The team discusses alternatives, keeps enough overlap for collaboration, and gives employees greater control. The manager changes their own schedule too. Morale improves as people feel trusted to manage their work. section 3.3.1

Flexibility is not the absence of coordination. It works when leaders remain clear about shared goals and collaboration needs while allowing reasonable variation in when, where, and how work happens. section 3.3.1 section 8.4.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Demonstrates flexibility through a workplace scenario and practical measures, stopping short of formal frameworks or technical implementation.
Examples
Uses revised core hours, adjusted manager schedules, work-from-home support, rampback programs, and no-meeting days.
What it assumes
Builds from everyday team scheduling and employee-support situations without requiring technical or specialized background.
What you can do after
Practice/perform it by gathering feedback, revising rigid policies, and balancing employee choice with collaboration requirements.
How it connects
Links flexibility with autonomy, collaboration, communication, hybrid work, employee satisfaction, motivation, and attrition.

Also explained in

Compare how 9 books explain flexibility →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.