Dream About Skates – Meaning

Skates describes the set of shortcuts, props and behaviors people use to glide past friction at work — the templates, quick fixes and visible signals that make progress look smooth even when underlying problems persist. It's important because these "skates" change how teams learn, how leaders judge progress, and whether real improvement ever happens.

What it really means

Skates are both artifacts (checklists, slides, dashboards) and behaviors (rehearsed answers, partial handoffs, temporary hacks) that reduce apparent resistance. They let people move faster or appear competent without addressing root causes. In practice, skates trade depth for mobility: they prioritize delivery of something that looks like progress over durable change.

How this pattern develops and stays in place

• Efficiency pressure: tight deadlines and output targets reward fast visible results over careful fixes.
• Rewarding appearances: promotions or recognition tied to deliverables encourage polished artifacts rather than messy iteration.
• Tool proliferation: more templates, scripts and dashboards make it easier to patch than to redesign.
• Low consequence for rework: if short-term fixes are tolerated, teams prefer them to costly redesigns.

These forces reinforce each other: when a quick script or slide gets rewarded, others copy it as an economical path forward. Over time the organization accumulates more skates, which makes the next shortcut even easier and the hard fixes harder.

How it appears in everyday work

• A team hands over a near-complete slide deck instead of a decision memo explaining trade-offs.
• Developers deliver a feature toggle that bypasses a fragile service rather than refactoring the service itself.
• Managers report on KPIs that are easy to update but don’t reflect customer experience.

In meetings you’ll hear rehearsed phrases, deferred acknowledgment of systemic issues, and lots of quick wins framed as long-term solutions. These visible artifacts reduce debate and make the group feel productive, even when underlying bottlenecks remain.

What makes it worse — and where leaders commonly misread it

• Leaders who equate speed with competence may approve skates as proof of performance.
• Incentives that reward appearance (e.g., polished presentations) encourage more skates.
• Siloed accountability lets groups apply local patches instead of coordinating a fix.
• Over-emphasis on short-term KPIs creates a culture of cosmetic fixes.

When leaders mistake polished artifacts for solved problems, they remove the pressure to address root causes. Teams learn that surface-level solutions are sufficient and stop escalating harder technical or organizational blockers.

How to reduce, change, or channel skates constructively

• Prioritize root-cause metrics alongside visible outputs (e.g., mean time to recovery, error recurrence rate).
• Make small investments in durable fixes part of the delivery definition ("done" includes a stability check).
• Reward learning and documented trade-offs, not just completion of artifacts.
• Introduce periodic forced refactor or process audits to remove accumulated skates.

These actions shift attention from short-term polish to longer-term resilience. They also provide a simple set of behaviors to replace skates with: document trade-offs, surface constraints, and make time for remediation.

A quick workplace scenario

A product team repeatedly ships copy changes that temporarily suppress a support spike. A manager notices lower ticket counts and praises the team. Instead of celebrating, the team documents the root cause (an onboarding step that misleads users), schedules a sprint to fix the flow, and adds a stability check to the definition of "done." The next time a ticket bump appears, the team evaluates whether a quick copy update or a product change is the proper response.

Related ideas and common confusions

• Workarounds vs. skates: workarounds are often ad-hoc, tactical fixes to keep operations running; skates include standardized shortcuts that become normalized and rewarded. The difference matters for whether the behavior gets institutionalized.
• Cosmetic compliance vs. genuine improvement: a polished report that hides unresolved risks is cosmetic. Genuine improvement shows durable change and transparent trade-offs.
• Confusion with agility: rapid iteration looks similar to skating if teams iterate on the surface without learning. True agility combines speed with validated learning.

Distinguishing these concepts helps teams decide whether to remove a skate, preserve a useful workaround, or convert a shortcut into a repeatable, resilient practice.

Questions worth asking before you act

• Does this deliverable hide unsolved problems or make them visible?
• Who will own the underlying issue if this quick fix fails?
• Is this behavior rewarded across the organization, or just in a local silo?

Answering these questions helps avoid mistaking sheen for substance and guides whether to tolerate, improve, or retire a skate.