Case Study: Scientific Equipment Manufacturer Adopts LiquidPlanner for All Product Development

June 2, 2017 by Sam SauerSam Sauer



At Lake Shore Cryotronics, a scientific equipment manufacturer, the lack of a project portfolio solution for project management made it difficult for the company’s 50-person product development team to track and manage its complex workload. The company’s move from Microsoft Project to LiquidPlanner gave the team a single view of resource allocation across all projects, including sustaining engineering work. The team can now quickly adjust to changing priorities, and is working together more effectively because LiquidPlanner pulls the entire team into the project management process—in a way that’s easy and natural for all.

Founded in 1968, Lake Shore Cryotronics develops, manufactures, and markets measurement and control sensors, instruments, and systems for precise measurement and control of temperature and magnetic fields. Users of these products are typically scientists, physicists, and researchers in universities, aerospace, government, and corporate R&D labs, with applications that range from electronics and clean energy to nanotechnology and deep space.

Download a PDF of this case study here.

The product development team at Lake Shore Cryotronics consists of about 50 people, including engineering technicians, design engineers, manufacturing engineers, software developers, and managers. At any time, the team’s workload includes roughly a dozen new product development projects, as well as a continual stream of sustaining engineering efforts. All team members support multiple new product development projects and are expected to ensure that sustaining efforts remain a high priority.

Prior to mid-2016, the product development team at Lake Shore Cryotronics lacked a comprehensive solution to all its project management needs. At the time, the company used Microsoft Project Professional. Each project resided in a standalone Microsoft Project file, and the team’s single Development Process Manager was the only Microsoft Project user.

“We chose to have only one person manage schedules due to the complexity of Microsoft Project,” says Rob Welsh, who assumed the role of Development Process Manager a few years ago, when the company decided it needed a full-time focus on project and process management.

During the planning phase for each new project, Welsh would work with that project team to define a work breakdown structure and project schedule, upon which Welsh would create a new Microsoft Project file. As the project progressed, Welsh used Microsoft OneNote to collect status updates from the project team. “We utilized OneNote to maintain project records and help keep project schedules updated,” explains Welsh. “Every week, for each project, I would create a table of current tasks in OneNote and ask the resources to update their progress and estimate remaining work. After I received that information, I used it to update the project schedule.”

The major problem with this method was that projects often deviated from the original plan very quickly. Technical issues, changing priorities, new tasks, and changing resource availability all resulted in the tasks that Welsh was asking people to update in OneNote each week not matching what they were actually doing. “The result was lower participation, inaccurate schedules, and reduced visibility to what people were working on,” says Welsh. “The only way to counter this was with frequent meetings that pulled entire project teams away from their work and negatively impacted project completion.”

As Welsh points out, all of this wasn’t due to poor planning or coordination. For example, during the course of a project, the team would often find a way to deliver greater value for customers. “The problem we had, however, was that we had no good way to determine the effect of that change on that project or other ones that shared the same resources,” Welsh explains. “This made it difficult to examine the tradeoffs, if any, and make quick yet fully-informed decisions on how to reallocate resources.”

Lake Shore Cryotronics now uses LiquidPlanner for all its project management needs. “Our adoption of LiquidPlanner was something that I initiated; there was no mandate from management,” Welsh explains. “We had already tried several approaches—to the point that most people were experiencing ‘changing project management methods fatigue’ and there was much skepti...

(RSS generated with FetchRss)

Previous Article
The Case for Multiple Project Management Methodologies
The Case for Multiple Project Management Methodologies

A multiple-methodology approach to project management may lead to happier project teams, according to a new...

Next Article
Advice for Project Managers: Good Questions to Ask in a Job Interview
Advice for Project Managers: Good Questions to Ask in a Job Interview

 Dear Elizabeth: I have an interview coming up. It’s important to me that I find a company with a cultur...