Balance Team Flexibility With Smartsheet

By Smartsheet on Jun 8, 2026

Flexibility vs. control isn't a values question—it's an infrastructure one. See how Smartsheet helps teams move fast while leaders keep visibility and alignment.

TABLE OF CONTENTS It's a Design Problem, Not a People Problem The Problem with Rules What Balance Actually Looks Like Scaling the Balance Across Teams and Portfolios How Real Teams Scale Successfully The System Empowers the Strategy

PARTNER PERSPECTIVES

This is sponsored content from Smartsheet. Learn here how we stay transparent.

There's a tension every project manager eventually encounters, which often shows up disguised as something else. Maybe your team is moving fast but nobody seems to be able to give you a clear status update. Or maybe you've got perfect visibility into every project, but everything is slow because nothing moves without layers of signoff.

Both problems look different on the surface. Underneath, they're the same: a misalignment between how much autonomy your team has and how much structure exists to support it.

In a recent report Smartsheet produced on project and portfolio management priorities, we found that 47% of professionals rank structure and flexibility as equally important for responding to change — so the tension is real. The question is what can PMs do about it?

Smartsheet is the shared work management platform that gives teams flexibility while giving leaders visibility, reporting, and governance.

It's a Design Problem, Not a People Problem

Project managers often diagnose these issues as people problems. The team isn't communicating. Stakeholders are micromanaging. Nobody's following the process. But in most cases, the process itself is what's broken — or may be completely missing.

Teams that operate with too little structure drift. Not because they don't care, but because without a clear, shared framework for how work gets tracked, reported, and escalated, everyone defaults to their own systems. Work gets done but alignment falls apart. Decisions get made in isolation. By the time problems surface, they're already expensive. Smartsheet addresses this directly: pre-built templates give teams a consistent starting point, shared dashboards surface status in real time, and automated alerts flag risks before they become blockers — so the framework exists without anyone having to build it from scratch.

Teams under too much control slow down for surprisingly similar reasons. When a team is drowning in meetings and reports, people start working around the system. Speed and governance end up in opposition. Smartsheet flips that dynamic: reports roll up automatically from live project data, so leaders get the visibility they need without pulling it manually, and teams spend their time on work rather than reporting on it.

Neither is a failure of intent. Both are symptoms of the same underlying gap: the absence of a system that gives teams enough room to move while keeping the organization informed and aligned. Structure and flexibility aren't actually opposites — they're complementary. The goal is building a system where both can synergistically coexist.

The Problem with Rules

When organizations try to regain control, they often default to implementing rules, but rules create limits. More process documentation. More required fields. More approval steps. The intention is right (consistency, accountability, predictability) but the result is usually the opposite. You end up with the appearance of governance, without the substance.

The better target is a repeatable system — one flexible enough to adapt to different project types and team contexts, but consistent enough that everyone is working from the same playbook. Smartsheet makes this practical: intake forms standardize how work enters the system, automated approvals move decisions through the right channels without manual follow-up, and role-based permissions ensure people see and act on exactly what's relevant to them. Workflow automation handles the handoffs. The result is governance that travels with the work — embedded in how the team operates, not layered on top of it as a separate task.

The goal isn't to micromanage outcomes. It's to create conditions where good outcomes are more likely.

What Balance Actually Looks Like

In practice, striking the right balance requires a few things working together.

Standardize inputs. What should be standardized is how work gets reported up: the status indicators, the milestone checkpoints, the risk flags. In Smartsheet, these inputs feed directly into portfolio rollups and dashboards, so portfolio-level visibility becomes automatic, not manually driven.
Build governance into the workflow. Automated approvals, role-based permissions, and pre-built intake forms are what make this possible at scale. In Smartsheet, these aren't add-ons. They're built into how workflows are configured, so the right thing stays the easy thing even as project complexity grows.
Match the methodology to the moment. Research from Smartsheet shows that 42% of teams have embraced hybrid project management. Smartsheet supports this natively: teams can manage work in different views, applying the right structure to each phase without fragmenting the data.
Give teams flexible tools. A shared platform like Smartsheet, with deep integration capability, lets teams work in the tools they prefer while keeping information in sync. Leaders get the portfolio-level view they need without requiring manual maintenance.

Scaling the Balance Across Teams and Portfolios

The challenge compounds as organizations grow. What works for a single team often doesn't hold when you're managing multiple functions, geographies, or business units. The seams — handoffs between teams, rollups across different project structures, decisions that require input from stakeholders who aren't close to the work — are where drift and gridlock tend to show up first.

One of the most underappreciated drivers of these problems at scale is what researchers call the "uniqueness bias": the tendency for project managers to assume their project is one of a kind. A Harvard Business Review study of 1,300 IT projects found that managers are highly prone to this thinking — and the more unique they rate a project, the worse it performs. The remedy isn't to treat every project as identical. It's to start from proven templates that encode what's known — intake forms, risk logs, milestone structures — and customize from there. This approach builds consistency where it matters without sacrificing the adaptability that different contexts require.

At scale, the system also needs feedback loops. What worked when you had five projects probably needs adjustment at fifty. Building in regular retrospectives, tracking core metrics like timeline variance and scope change, and staying open to iterating on the system itself is what separates organizations that mature their PM practice from those that just add more process when something goes wrong.

How Real Teams Scale Successfully

Here are a few real-world examples of how the right project management software can drive productivity while still being flexible.

Infosys faced the challenge of scaling consistent project delivery across a global workforce without sacrificing speed. By standardizing workspace deployment through Smartsheet templates, they brought new programs online quickly with governance requirements encoded from the start — while giving delivery teams flexibility to manage day-to-day execution in ways that fit their context.
Roche's PMO needed to improve delivery predictability across a complex portfolio without creating a bottleneck at the center. Standardizing how projects tracked and reported status in Smartsheet gave the PMO automatic portfolio-level visibility, while individual teams kept autonomy over their own work — meaningful productivity gains without sacrificing team-level agility.
Puma needed enterprise-scale integration without overhauling the processes already in place. Smartsheet's integration architecture connected existing tools and workflows rather than replacing them, giving the organization a coherent view of work in progress while teams continued working in systems they already knew.
Ogilvy manages work across a distributed workforce where no two engagements look alike. Using Smartsheet for media asset tracking and status reporting, project leads can see the state of every detail across engagements, spot risks early, and keep leadership informed — without constant manual reporting.

The System Empowers the Strategy

There's a tendency to treat the flexibility-versus-control question as a values question. How much oversight is too much? It's actually an infrastructure question. The organizations that get this right aren't the ones that find the perfect philosophical answer. They're the ones that build systems thoughtful enough that the question stops coming up.

That means templates that encode best practices without locking teams in. Governance that travels with the work rather than sitting alongside it. Tools that flex to the team without fragmenting the data that leaders need. And feedback loops that let the system improve over time, rather than calcify into the next set of rules nobody follows.

Structure and flexibility stop being in tension when the system is smart enough that teams don't have to choose between them.

Ready to give your teams room to move without losing visibility, alignment, or governance? Explore Smartsheet and see how the right platform makes speed and structure work together. Get started today.