Project & Process Management for a Tech-Driven Workplace

e.g. This is primarily aimed at first- and second-year undergraduates interested in engineering or science, along with high school students and professionals with an interest in programming.Digital tools can either make project work smoother—or multiply chaos. In this course, you’ll learn how to design clean, async-first workflows that help teams move faster with fewer meetings, clearer ownership, and better visibility. You’ll start by building strong documentation habits: establishing a single source of truth, using simple templates, and organizing a lightweight knowledge base that stays searchable and up to date. Next, you’ll design practical “flow in tools” systems: structured intake and triage, decision logs that prevent rework, and embedded ownership practices (like RACI) inside the tools your team already uses. You’ll then learn how to apply automation safely—using triggers and actions to reduce manual coordination—plus how to build dashboards that support the right decisions for teams, PMs, and stakeholders. Finally, you’ll apply AI in realistic PM work: generating first-draft plans and work breakdowns, drafting clearer status updates and stakeholder communication, and scanning project artifacts for risks and improvement opportunities—with guardrails for privacy and human oversight. You’ll leave with reusable templates, prompt patterns, and governance rules you can apply immediately.

Your day is packed. Slack never stops. Meetings fill the calendar. And somehow… the most important work still doesn’t move. That’s not a personal productivity problem—it’s a process flow problem. In Lean Management & Process Flow for Knowledge Work, you’ll learn how to see digital work as a system: how requests move from idea to delivery, where they get stuck, and what to change to deliver faster without burning out your team. This course takes lean principles beyond manufacturing and applies them to modern knowledge work—product, marketing, software, ops, support, internal platforms—any environment where work is invisible, highly collaborative, and constantly interrupted. By the end of the course, you’ll be able to: • Define value for different kinds of teams—and spot the most common forms of waste in digital workflows (waiting, rework, handoffs, “work about work,” and more) • Map a real value stream (idea/request → delivered outcome) to reveal bottlenecks, queues, and hidden delays • Measure flow using practical metrics like lead time, cycle time, and throughput—and interpret what the numbers are actually telling you • Set up a Kanban system with WIP limits to reduce multitasking and improve delivery predictability • Use Little’s Law as a simple reality check to connect WIP, throughput, and lead time (without getting lost in math) • Identify the true bottleneck in a workflow and choose the right fix—capacity, arrival rate, batch size, upstream quality, or expectations • Create lightweight service level expectations (SLEs) so stakeholders know what to expect—and trust improves • Build SOPs and checklists that reduce rework and make quality repeatable (without turning into bureaucracy) • Run small, experiment-driven improvements that compound over time: hypothesis → change → measure → learn → standardize You won’t just learn concepts—you’ll practice them. Each module includes scenario-based quizzes and applied exercises (like mini value-stream maps, flow-metrics interpretation, WIP-limit tuning, bottleneck diagnosis, and a capstone-style improvement plan). Who this course is for: managers, team leads, project/program managers, product and engineering leaders, operations and marketing leads—anyone responsible for improving how work gets done across people, tools, and handoffs. Recommended background: no lean experience required. If you’ve ever dealt with unclear ownership, endless review cycles, overloaded teams, or “everything is urgent,” you’re ready. If you want your team to ship value more consistently—with less chaos, less rework, and fewer fire drills—this course will give you the system, the metrics, and the playbook.

e.g. This is primarily aimed at first- and second-year undergraduates interested in engineering or science, along with high school students and professionals with an interest in programming.Managing projects is rarely about perfect plans—it’s about staying effective when requirements are fuzzy, dependencies shift, and surprises show up mid-delivery. Managing Project Uncertainty gives you a practical system for turning ambiguity into clear action. You’ll learn how to spot risk early, write risks in a cause → event → impact format, and score them using a simple likelihood × impact approach. From there, you’ll build a working risk register with owners, mitigations, and triggers—then run lightweight weekly risk reviews and track risk burndown so exposure decreases over time. When decisions must be made with incomplete information, you’ll use decision frames, timeboxes, and an upgraded decision log that captures assumptions and what to monitor. The course also equips you with fast root-cause tools (A3 thinking, 5 Whys, fishbone diagrams, and a lightweight FMEA) to prevent repeat failures. Finally, you’ll learn incident and post-mortem playbooks, empathy interviewing to surface hidden risks, and de-escalation scripts for difficult conversations under pressure. By the end, you’ll be able to lead calmer, clearer project execution—even when the path isn’t fully visible.

Most organizations don’t struggle because teams can’t execute—they struggle because too many initiatives compete for the same people, dependencies stay invisible, priorities flip midstream, and “green” projects don’t add up to real business value. In this course, you’ll learn how to manage programs and portfolios as a system, not a pile of disconnected projects. You’ll start by distinguishing projects, programs, and portfolios—and how that choice changes how you plan, measure, and lead. Next, you’ll set portfolio-level objectives, apply simple value scoring to prioritize initiatives, and build an initiative inventory that makes work visible and comparable. From there, you’ll map cross-team dependencies, visualize risk with heatmaps, and plan realistically using capacity and historical throughput to avoid the overstuffed roadmap. Finally, you’ll design lightweight change control and governance that keeps decisions moving without bureaucracy, then connect delivery to outcomes through benefits realization, OKRs, and KPIs. By the end, you’ll be able to prioritize better, coordinate across teams, and run portfolio reviews that drive clear decisions to stop, pivot, continue, or scale initiatives.