• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
See to Solve

See to Solve

Succeeding Starts With Seeing

  • Alert
  • Flow
  • Resources
    • Success Stories
    • Webinars
    • Podcasts
    • Blog
  • About Us
  • Contact Us
  • Request A Demo

How do you get speed in technology intensive, engineering heavy situations?

October 30, 2020 by See To Solve

Slow down (in development) to go fast (in deployment and production). Local experience gives example to this point and might provide insight to the many of use trying to develop and deliver value at speed. (Boston Globe article and white paper).

The Massachusetts Bay Transportation Authority (“MBTA”) is under fire. New subway cars, meant for the T’s Orange and Red lines are being delivered late and underperforming from Chinese state-sponsored vendor CRRC.

Easy explanation: bureaucratic incompetence, perfidiousness by the foreign vendor, etc. More likely, both CRRC and MBTA had reason to get into operation as quickly as possible. Consequently, they didn’t recognize how much more developmental work had to be done–tailoring the product to Boston area use, debugging a new, in-state production facility, training more deliberately the new workforce.

In a rush to “get on with the real work,” they each short changed the capability building necessary to have operations that run silky smooth. To go fast, they went to fast (when they shouldn’t have), and so are going too slow now.

The alternative: go slow (allow time to do the active experimentation development) when capability is being built to go wicked fast when systems are actually on line.

There are lessons for both vendors (to bid with developmental time built in) and buyers (to realize that before thinking in terms of dollars per unit they have to budget for ideas per hour).

The Boston Globe’s Adam Vaccaro wrote a piece about this situation, “Long before pandemic, problems mounted for new Red and Orange line cars.”

I’ve written a longer thought piece exploring this distinction between developmental and routine-production modes. <–click to download.

Looking forward to your feedback and comments.

Very best,
Steve

PS: Check out our See to Solve systems, portable andons and virtual processing mapping tools to make the hidden visible.

Down load “Getting the T Back on Track“
Steven Spear DBA MS MS
Principal, See to Solve LLC
Senior Lecturer, MIT Sloan School of Management
Senior Fellow, Institute for Healthcare Improvement
Author, The High Velocity Edge

Filed Under: Blog

Primary Sidebar

Featured Posts

Hospital System Dramatically Improves Sterile Processing Performance Helped by See to Solve Alert™

GSK Uses See to Solve Alert to Fix Problems Faster in Multi-Disciplinary ‘Smart Labs’

Baptist Memorial Hospital-Memphis Adopts See to Solve
Alert™ to Speed Problem Resolution

Solidigm Adapts Process Mapping to Remote Work with See to Solve Flow™ and Accelerates Improvement

Podcast Episode: Exploring COVID-19 and Just-in-Time Supply Chains, Chaos Engineering, and the Soviet Centrally Planned Economy with Dr. Steve Spear

Footer

See to Solve

  • Email
  • LinkedIn
  • YouTube

Products

  • Alert
  • Flow

Resources

  • Contact Us
  • Blog & News

See to Solve

343 Washington Street, Suite 203
Newton, MA 02458
United States

Phone: +1 (201) 705-1000
Email: [email protected]

Copyright © 2023 · See to Solve, LLC · All Rights Reserved