Mick P.

I help businesses understand how work actually gets done, turn complex workflows into clear processes, and translate business needs into structured software requirements. My work typically starts with one of two needs: 1. “We need to understand and document this process.” I map current-state and future-state workflows, clarify roles and handoffs, uncover bottlenecks and exceptions, and turn tribal knowledge into structured process documentation. 2. “We know the business process—now we need to define what the software must do.” I translate business processes and stakeholder needs into clear business and software requirements that can support software selection, development, migration, or implementation. What I Do Best • Current-state and future-state process mapping • Business process analysis and improvement • Stakeholder interviews and discovery • Swimlane diagrams, flowcharts, and SIPOCs • Activity inventories and process decomposition • Bottleneck, rework, handoff, and ownership analysis • Business requirements gathering and documentation • Business Requirements Documents (BRDs) • Software and functional requirements • SOP and procedure development Typical Projects Clients hire me to: • Understand how work actually flows across teams and systems • Document complex or poorly understood business processes • Capture tribal knowledge before it becomes a business risk • Identify bottlenecks, redundant work, unclear ownership, and broken handoffs • Establish a reliable current state before a process or technology change • Gather and structure requirements from multiple stakeholders • Translate operational needs into software requirements • Develop BRDs or requirements documentation for system selection, migration, or development • Map current-state processes and design practical future-state workflows How I Work I typically begin with stakeholder interviews, existing documentation, and activity discovery to understand the work before documenting the solution. For process-mapping engagements, I structure the current state, validate it with the people doing the work, and make the decisions, dependencies, exceptions, and handoffs visible. For requirements engagements, I use that understanding of the business process to identify what the organization actually needs from the software and translate those needs into clear, structured requirements. Depending on the engagement, deliverables may include process maps, swimlane diagrams, SIPOCs, activity inventories, BRDs, business and software requirements, SOPs, future-state workflows, and improvement recommendations. The objective isn't documentation for documentation's sake. It's to create enough clarity about the business and its requirements to make better operational and technology decisions. Experience & Tools 35 years of operations and enterprise systems experience, including 20+ ERP implementations, with an MBA, Lean Six Sigma Black Belt, CPIM, and Certified Agile Leader credentials. Tools & Methods: Microsoft Visio • Lucidchart • Miro • BPMN • SIPOC • Google Workspace • Notion If you need to understand how a business process works—or translate that process into clear requirements for a system or software initiative—I can help bring structure to it quickly.