Concise Actions
Concise actions provides a fully customizable, self-service task management system that allows users to create, assign, and track complex, multi-step remediation and recovery plans directly within the platform.
The Vision
The vision for this product was to transform the platform from a system that merely reports data into a proactive, collaborative command center for operational execution. The goal is to give users the power to define, automate, and execute their own custom remediation and recovery plans, moving them from simply identifying a problem to immediately and effectively acting on a problem.
The PM Architecture
The solution was built around three core, collaborating components:
​
-
Presentation Layer: The user interface responsible for defining the workflow, including the Workflow Builder (which serializes complex task sequences into machine-readable format) and the Filtering Module (which applies criteria like Supplier or Part to target the workflow).
-
Core Services Layer (The Engine): The backbone where the logic lives:
-
Task Management Service (TMS): Manages the entire state of the workflow—instantiating all necessary tasks based on filters and tracking every dependency and task status.
-
Rules Engine: The critical component that executes the conditional automation logic defined by the user (e.g., if a form field is submitted, automatically mark the next task as complete).
-
-
Data Layer: Stores the Task Graph (the live map of all running tasks and dependencies) and maintains an Audit/Event Log to record every action and justification for compliance and historical review.
PM x Engineering Collaboration - Agile Development
The success of this project relied on a tightly integrated Agile process that ensured technical feasibility aligned with business value at every step.
-
Iterative Blueprinting & Story Definition (PM-Led): As the Product Manager I defined the project's phased scope (MVP first, then scaling features) and translated the complex vision (e.g., self-service rules) into granular user stories and clear acceptance criteria. Critically, I prioritized user experience, specifically mapping out the required UI flows for complex components like the Rules Engine and Advanced Filters before Engineering began development, preventing costly refactoring.
-
Architectural Design & Technical Feasibility (Engineering-Led): Engineering owned the architectural design of the scalable, modular services, such as the Task Management Service and the core Rules Engine. They engaged in early, frequent collaboration with me to define technical constraints, estimate effort, and propose solutions for the underlying data structures, ensuring the architecture could support my long-term vision
Problem Solving & Edge Cases
The teams maintained a continuous feedback loop through structured problem-solving sessions like joint sprint review/planning, scope alteration etc. I usually presented high-risk scenarios and edge cases like dependency failures, data corruption in a task etc to Engineering, who then validated the system's resilience and built the necessary failure mode logic. This iterative partnership ensured the final product was not only functional but also highly robust and reliable for critical operational use.
Result
The successful launch of the concise actions feature immediately transformed the product from a static reporter to a dynamic operational hub. The project delivered self-service custom workflow creation and a Rules Engine that automated remediation processes, resulting in a significant acceleration of organizational recovery time during disruptive events. This shift drove higher feature adoption and established the platform as the central, auditable system for managing and executing complex business processes.
Wireframes & Concepts
