Schedule Manager for Non-Professional / Accidental Project Managers

Sources:

• https://blogs.sw.siemens.com/teamcenter/schedule-management-and-the-accidental-project-manager/
• https://blogs.sw.siemens.com/teamcenter/PLM-Project-Management-for-the-Masses/ (author: Susan Zimmerlee, Siemens)

These two Siemens blog posts are notable because they document real, informal, non-enterprise use of Schedule Manager — useful evidence that the tool is usable well below the "formal program office" scale often assumed in official documentation.

Three Core Capabilities Called Out for Non-PM Users

1. Connect tasks to actual work — link schedule tasks directly to PLM data so team members get exactly what they need without hunting across systems; deliverables get captured automatically as work progresses.
2. Attach workflows to scheduled tasks — e.g., a document-creation task can drive a full create/review workflow, and task status is pulled from workflow completion rather than manually toggled.
3. Automatic status updates — "As users complete their work, the task status is automatically updated. No more phone calls or emails" to chase status before a review meeting.

Real Example: Susan Zimmerlee's Blog-Coordination Schedule

Zimmerlee (a Siemens content coordinator, not a professional project manager) describes using Schedule Manager to solve a personal coordination problem — tracking blog post deadlines and reminders across multiple product managers' contributions over a six-month content calendar.

The problem in her words: "Sometimes I get busy with another project and forget to check the calendar. Or sometimes I don't get a draft when I expect it, and don't follow up quickly enough…"

Her solution:

• Requested access to Schedule Manager (framed internally as a tool "for the program office," not for individual contributors — worth noting as an adoption/access-control consideration).
• Built a personal template ("Susan's Blog Schedule") with one master task and four subtasks:
  • Reminder #1 — six weeks out
  • Reminder #2 — four weeks out
  • Draft Due — deadline day
  • Post Blog — publish deadline
• Set up task dependencies within the template, then duplicated the template across her six-month pipeline (one instance per blog post).

Result reported: "Now I get reminders when I need them and things are getting done on time!"

Takeaway for Implementers

This is a concrete, attributable example of the "use templates to avoid rebuilding recurring schedules from scratch" best practice (see the pitfalls/best-practices file) applied outside a formal program context — worth citing when advocating for broader Schedule Manager access within an organization beyond the core PM/scheduler role, and as a pattern for any recurring, template-shaped internal process (not just blog publishing).