📋

Project & Process Management Topics

Project management methodologies, process optimization, and operational excellence. Includes agile practices, workflow design, and efficiency.

Technology Evaluation and Vendor Management

Selecting and integrating third-party technology: evaluating tools and platforms, vendor and technology assessment, procurement, and managing implementation and integration projects. Covers structured buy-versus-build and vendor-selection reasoning and running the resulting implementation.

44 questions

Structured Problem Solving and Decomposition

Methodical problem solving for open-ended and ambiguous situations once the problem is defined: decomposing a goal or problem into mutually exclusive, collectively exhaustive parts (issue trees, metric trees and driver breakdowns, work breakdown into subproblems and vertical slices), forming and prioritizing hypotheses (hypothesis trees and funnels, including laying out candidate explanations for a metric drop or model degradation and the cheapest test for each branch), choosing an analytical approach, and reasoning to a recommendation. Also covers turning a vague mandate into measurable, testable subproblems with owners, breaking a large initiative into workstreams, mapping dependencies, sequencing the work, deciding the first deliverable and what to defer, structuring plans that mix research, analytics and experiments, and talking through real examples of cutting a messy problem into parts. Covers explaining and adapting structured problem-solving methods across contexts, choosing and switching methods, and coaching others to structure ambiguity. Excludes turning a vague request into a scoped problem statement, named-framework business cases, root-cause techniques for failures and metric movements (running the diagnosis itself), prioritization scoring and trade-off decisions, deciding how to act under incomplete information, market sizing and estimation, and framing machine-learning problems, which are covered elsewhere.

20 questions

Process Metrics and Operational KPIs

Measuring and managing processes with data: selecting operational KPIs, building visibility and dashboards, and driving process decisions from metrics rather than intuition. Covers defining the right measures for a process and using them to detect drift and prove improvement.

3 questions

Project Delivery and Execution Ownership

Individually taking accountability for a project or initiative and driving it from kickoff to a shipped, committed outcome. Covers defining goals and measurable success metrics, scoping and decomposing the work, planning milestones and managing risk and dependencies, unblocking work and escalating when genuinely needed, adapting the plan under real-world constraints (deadlines, incomplete resources, ambiguous requirements), monitoring delivery health, and closing the loop on committed results. Equally covers the initiative side of ownership: acting with bias to action rather than waiting for permission, proactively identifying and fixing problems no one assigned, following through on commitments with limited oversight, and judging the right scope for unprompted initiative. Applies across technical and non-technical roles and at any level, from a first project to a cross-team program. Distinct from: narrating or selecting a single standout achievement or portfolio (Proudest Achievements and Project Portfolio); diagnosing and improving a recurring, systemic process (Process Improvement and Root Cause Analysis); the mechanics of coordinating with or negotiating between other teams whose incentives differ (Cross-Functional Collaboration); setting technical direction or influencing a strategic technical decision (Technical Leadership and Strategic Influence); the technique of managing stakeholder relationships and expectations as its own skill (Stakeholder Management and Alignment); the craft of communicating upward to executives (Executive Communication and Managing Up); and the candidate's own career trajectory or promotion path (Career Goals and Progression).

49 questions

Documentation and Knowledge Management

Governing how teams capture and keep knowledge usable: documentation standards, ownership models (centralized, federated or dedicated team) and review cadences, incentives and culture change that get engineers to document, decision records and assumption logs, post-project reviews that preserve lessons, and knowledge-base strategy so organizational knowledge stays findable and attributed. Includes building or buying a knowledge platform, migration and consolidation plans, taxonomy, tagging and search quality, linking docs to code, capturing tacit expertise into the knowledge base, detecting and remediating stale docs across a documentation estate, and versioning and change policies for shared reports and metric definitions. Covers the governance and lifecycle of a body of documentation, not the craft of writing any single document.

9 questions

Automation and Toil Reduction

Deciding what manual, repetitive work is worth automating and proving it paid off. Covers identifying and inventorying toil, scoring and prioritizing automation candidates, break-even and ROI arithmetic including maintenance cost, choosing an automation approach (robotic process automation, scripts, no-code tools, rules engines, ML-assisted triage, self-service) and migrating legacy spreadsheet or macro processes, when not to automate, safeguards and governance for automation that touches production or business-critical processes (dry-run, approvals, audit trail, ownership, rollout and rollback), finding opportunities through ticket data or process-discovery analysis, measuring automation health and impact (including diagnosing regressions and attributing impact), cataloguing existing automations, making the business case to leadership, and managing the people side (adoption, reskilling, stakeholder concerns). Applies to operations, data and business-process work alike. Excludes writing the automation itself (scripts, infrastructure-as-code, pipelines, orchestrator internals), the definition of toil as reliability doctrine, and incident response mechanics.

10 questions

Process Analysis and Improvement

Understanding and improving how work gets done end to end: current-state and future-state process mapping, business process modeling, workflow visualization, and gap and root-cause analysis to make an existing process legible so it can be diagnosed. Covers systematically improving the process with Lean and Six Sigma methods, continuous improvement, bottleneck resolution, and root-cause-driven optimization, and building an operational-excellence culture.

43 questions

Progress Tracking and Status Reporting

Keeping a project visible and on track: tracking progress, monitoring project health with early-warning signals, and reporting status to stakeholders and executives. Covers choosing status metrics, surfacing problems early, and tailoring communication to different audiences.

40 questions