Case study · Midwestern Engineers
Planning inside the system Midwestern already used
Midwestern Engineers already had production assignments in its application. We built the planning view around those records, keeping dates, ownership, and the latest note connected to the work.
- Starting point
- An existing business application
- Build scope
- A planning view within that system
- Context kept together
- Dates and the latest note
A production schedule has to answer more than one question. A project lead may need to see everything assigned to one job. A team lead may need to understand the work carried by a group. Someone planning across the business may need to look at each engineer’s assignments over time.
Midwestern Engineers wanted an intuitive, customizable Gantt view that worked with the tools already in use. The important design decision was to let people change the way they looked at the schedule without creating a second schedule to maintain.
One assignment, three planning questions
The planning view starts with a production assignment. That record holds the project, assigned team, engineer, start and end dates, assignment type, and latest note.
The same assignments can be viewed by project, team, or engineer. A different view changes the planning question, while the dates and the latest note remain attached to the assignment.
Production schedule
No assignments match “”.
Keep the context near the decision
A bar on a timeline is useful only when someone can tell what it represents. In the Midwestern planning view, staff can open an assignment to inspect its project and ownership, change its dates or assignee, and read the latest production note alongside the work. The schedule can also be exported as a consolidated PDF when the plan needs to leave the application.
Those details matter because scheduling questions rarely arrive one at a time. Moving an assignment can affect a project plan, a team’s workload, and an engineer’s calendar at once. Keeping those perspectives tied to the same record makes it easier to review the consequence of a change before treating it as settled.
Review the work in its actual context
Using the existing production assignments gave Midwestern something concrete to review: how its work was organized, which details belonged on the timeline, and what someone needed to change from the same screen. The planning view stayed close to the project and staffing information it was meant to clarify.
Matt Clarke, Midwestern’s IT Manager, described the result this way:
“The final product has enhanced our ability to coordinate and monitor timelines across our business.”