#function column

[clovisresearch]

Swimlanes as Data: Normalize Function Data (Post 2)

Swimlanes as data: normalize function data (post 2) Swimlane diagrams do not usually “break” because the process changes. They break because lane names drift. It starts small: • “Operations” becomes “Ops” • “Customer Success” becomes “CS” • someone adds a trailing space • a contractor types “Finance / AP” for the same lane the team calls “Accounts Payable” Then Visio Data Visualizer imports the dataset and suddenly: • 2 lanes appear where there should be 1 • steps move into the wrong lane • handoff counts become meaningless • the diagram looks “wrong” and people stop trusting it This is why the Function column (the swimlane owner field) needs normalization. Normalization is not theory. It is simple hygiene. A reliable workflow: 1. Extract the unique Function values from the dataset 2. Choose 1 canonical name for each lane 3. Build a mapping table (alias → canonical) 4. Replace aliases in the dataset using a lookup 5. Lock it down with data validation (drop-down list) 6. Add short definitions so classification stays consistent 7. Repeat the same method for every future lens dataset Practical Excel moves that make this fast: • TRIM to remove invisible spaces • CLEAN to remove non-printing characters • XLOOKUP to map aliases to canonical lane names • Data Validation to prevent new drift Example: Ops | Operations | Operations Team | Ops (with a trailing space) All become: Operations Now every count, pivot, and diagram import becomes predictable. A decision that matters: What does Function represent? It can be: • Department lanes (good for accountability and handoffs) • Role lanes (good for staffing and approvals) • System lanes (good for automation and integration) The mistake is mixing these in one dataset. The clean approach: Keep 1 canonical dataset, then create derived lens datasets. Same Step IDs. Same Next Step IDs. Same flow. Only Function (and optionally Phase) changes to create the view needed for the decision. The payoff is immediate. Once Function is normalized, the dataset becomes a reliable system of record: • lane changes are intentional, not accidental • re-orgs are handled with a mapping update, not diagram surgery • handoffs can be counted (Function changes across connected steps) A governance rule that saves weeks: Keep a “Lane Dictionary” sheet. Lane (canonical) | Aliases | Definition | Owner | Last reviewed date Quick test: Import 20 steps, then deliberately change 1 Function value and re-import. If the lane moves exactly as expected, normalization is working. Normalize Function first. Everything else gets easier after that. #Visio #SwimlaneDiagram #ProcessMapping #DataQuality #BusinessAnalysis #DataVisualizer #Operations process improvement, process mapping, operations, business analysis, workflow, visio, swimlane, automation, lean, standard work

[clovisresearch]

Swimlanes as Data: The Function Field (Post 1)

Swimlanes as data: the function field (post 1) Most “swimlane diagrams” fail for 1 simple reason. The swimlanes are trapped inside the drawing. That means every organizational change, every role tweak, and every “can you show it by system instead?” request turns into diagram surgery: moving boxes, nudging connectors, cleaning up formatting, exporting again, repeating. Visio Data Visualizer works differently. In Data Visualizer, swimlanes are not “drawn”. They are assigned. The lane label comes from 1 column in the dataset: Function = the swimlane owner for that step. That is the unlock. Once Function is data, the swimlanes become a controlled field that can be changed in Excel and re-rendered in Visio on demand. A practical way to use it: 1. Keep Step IDs stable 2. Keep Next Step IDs stable (those define the arrows) 3. Use Function for the lane assignment 4. Optionally use Phase for columns (stage, lifecycle, etc.) Then the workflow becomes: • Update ownership = change 1 cell in Function • Re-org = remap Function values with a simple lookup table • New “view” = create a copy of the dataset and reclassify Function for the lens Common choices for Function: • Department (Sales, Finance, Operations) • Role (Analyst, Manager, Reviewer) • System (SAP, ServiceNow, Email, Spreadsheet) • Lens categories (Value-Added, Business-Value-Added, Non-Value-Added) The 1 rule that keeps it sane: Each step should have 1 primary lane owner. If multiple owners exist, capture them in a separate column (Secondary Owner) or split the step. Otherwise the swimlane view becomes ambiguous and handoff counts become unreliable. Common Function mistakes that create bad diagrams: • Same lane written 3 ways (Ops, Operations, Operations Team) • Trailing spaces that create “phantom lanes” • Over-granularity (40 lanes that no one can read) • Under-granularity (1 lane called “Team” that hides handoffs) A simple quality checklist: • 1 canonical name per lane • No blanks in Function • Lane names reflect the decision the diagram must support • The dataset imports cleanly every time (no surprises) Why this matters commercially: When swimlanes are data, Excel can quantify the map: • handoffs (lane changes) • approvals (tagged steps) • rework loops (back edges) • where work clusters by owner And that is what leaders actually want from “a swimlane diagram”. Not a picture. Insight and decision support. Quick test: Convert 20 steps, import once, then change 1 Function value and refresh. If that round-trip works, the process map just became maintainable. #Visio #SwimlaneDiagram #ProcessMapping #BusinessAnalysis #DataVisualizer #Operations Next move: normalize the Function field first, then scale conversion. That prevents drift and keeps every future view fast to produce. process improvement, process mapping, operations, business analysis, workflow, visio, swimlane, automation, lean, standard work

[clovisresearch]

Swimlanes as Data: The Function Field (Post 1)

Swimlanes as data: the function field (post 1) Most “swimlane diagrams” fail for 1 simple reason. The swimlanes are trapped inside the drawing. That means every organizational change, every role tweak, and every “can you show it by system instead?” request turns into diagram surgery: moving boxes, nudging connectors, cleaning up formatting, exporting again, repeating. Visio Data Visualizer works differently. In Data Visualizer, swimlanes are not “drawn”. They are assigned. The lane label comes from 1 column in the dataset: Function = the swimlane owner for that step. That is the unlock. Once Function is data, the swimlanes become a controlled field that can be changed in Excel and re-rendered in Visio on demand. A practical way to use it: 1. Keep Step IDs stable 2. Keep Next Step IDs stable (those define the arrows) 3. Use Function for the lane assignment 4. Optionally use Phase for columns (stage, lifecycle, etc.) Then the workflow becomes: • Update ownership = change 1 cell in Function • Re-org = remap Function values with a simple lookup table • New “view” = create a copy of the dataset and reclassify Function for the lens Common choices for Function: • Department (Sales, Finance, Operations) • Role (Analyst, Manager, Reviewer) • System (SAP, ServiceNow, Email, Spreadsheet) • Lens categories (Value-Added, Business-Value-Added, Non-Value-Added) The 1 rule that keeps it sane: Each step should have 1 primary lane owner. If multiple owners exist, capture them in a separate column (Secondary Owner) or split the step. Otherwise the swimlane view becomes ambiguous and handoff counts become unreliable. Common Function mistakes that create bad diagrams: • Same lane written 3 ways (Ops, Operations, Operations Team) • Trailing spaces that create “phantom lanes” • Over-granularity (40 lanes that no one can read) • Under-granularity (1 lane called “Team” that hides handoffs) A simple quality checklist: • 1 canonical name per lane • No blanks in Function • Lane names reflect the decision the diagram must support • The dataset imports cleanly every time (no surprises) Why this matters commercially: When swimlanes are data, Excel can quantify the map: • handoffs (lane changes) • approvals (tagged steps) • rework loops (back edges) • where work clusters by owner And that is what leaders actually want from “a swimlane diagram”. Not a picture. Insight and decision support. Quick test: Convert 20 steps, import once, then change 1 Function value and refresh. If that round-trip works, the process map just became maintainable. #Visio #SwimlaneDiagram #ProcessMapping #BusinessAnalysis #DataVisualizer #Operations Next move: normalize the Function field first, then scale conversion. That prevents drift and keeps every future view fast to produce. process improvement, process mapping, operations, business analysis, workflow, visio, swimlane, automation, lean, standard work