<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Solveboard]]></title><description><![CDATA[Empowering Your Management Journey with Expert Guides]]></description><link>https://www.bradluffy.com/execution</link><generator>RSS for Node</generator><lastBuildDate>Mon, 18 May 2026 12:19:24 GMT</lastBuildDate><atom:link href="https://www.bradluffy.com/blog-feed.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[OneRoute for Meetings]]></title><description><![CDATA[Most meetings fail not because people are unprepared, but because the meeting itself is never treated as a unit of work. OneRoute applies a single, structured execution path to meetings—separating preparation, discussion, decision-making, and closure—so meetings end with clear outcomes instead of lingering confusion.]]></description><link>https://www.bradluffy.com/post/oneroute-for-meetings</link><guid isPermaLink="false">69823a16aa13a366d93d6d75</guid><category><![CDATA[OneRoute]]></category><pubDate>Tue, 03 Feb 2026 18:30:19 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/a989e3_927d6bb37dfb4c19bbe2231f0084e25e~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>bradluffy</dc:creator></item><item><title><![CDATA[FLOW in Workforce Allocation]]></title><description><![CDATA[Workforce allocation doesn’t break because people can’t handle the work. It breaks when organizations misclassify the scale of a single unit of effort. This post shows how one assignment decision can range from a local task to a system-level concern — and why FLOW helps leaders escalate structurally instead of emotionally.]]></description><link>https://www.bradluffy.com/post/flow-in-workforce-allocation</link><guid isPermaLink="false">698234f0aa13a366d93d6358</guid><category><![CDATA[FLOW]]></category><pubDate>Tue, 03 Feb 2026 18:07:31 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/a989e3_59f5f4d42b1a4373987934bbcd2db399~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>bradluffy</dc:creator></item><item><title><![CDATA[Competitive Scenario Planning, Constrained by Design]]></title><description><![CDATA[This post examines how two runs of the same Competitive Scenario Planning artifact—using different levels of input detail—produced materially different outputs. By comparing sparse and richer inputs, it shows how SolveBoard’s governed AI artifacts preserve intent, constrain analysis, and make the relationship between inputs and outputs explicit.]]></description><link>https://www.bradluffy.com/post/competitive-scenario-planning-constrained-by-design</link><guid isPermaLink="false">69810dc0e90da4b7522c586f</guid><category><![CDATA[Artifacts]]></category><pubDate>Mon, 02 Feb 2026 21:11:41 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/a989e3_764cffc3ef3d4c07ac1f4bec91b91644~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>bradluffy</dc:creator></item><item><title><![CDATA[OneRoute for Customer Support]]></title><description><![CDATA[Customer support often feels chaotic—but it doesn’t have to be. This post shows how OneRoute turns a common account access issue into a single, structured workflow using clear ACTION, DECISION, and CUE steps. By designing support as a linear route instead of a reactive scramble, teams gain clarity, consistency, and control—without sacrificing speed or human judgment.]]></description><link>https://www.bradluffy.com/post/oneroute-for-customer-support</link><guid isPermaLink="false">6981028a99fa9e70ea602d76</guid><category><![CDATA[OneRoute]]></category><pubDate>Mon, 02 Feb 2026 20:29:46 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/a989e3_c22498631efc470a8ea2ae9495d19a21~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>bradluffy</dc:creator></item><item><title><![CDATA[FLOW in Supply Chain Risk]]></title><description><![CDATA[Most organizations don’t fail at supply chain risk because disruptions occur. They fail because they misclassify them. This Workbench post applies the FLOW framework to a single supply disruption to show how the same unit of effort can move across FLOW levels as complexity and scale change — and why getting that classification right is the difference between routine management and constant escalation.]]></description><link>https://www.bradluffy.com/post/flow-in-supply-chain-risk</link><guid isPermaLink="false">6967b4cd7d3bee3fd1044f10</guid><category><![CDATA[FLOW]]></category><pubDate>Mon, 02 Feb 2026 19:51:08 GMT</pubDate><enclosure url="https://static.wixstatic.com/media/a989e3_9a376ff6d57f40a4917191077907d5b4~mv2.png/v1/fit/w_1000,h_1000,al_c,q_80/file.png" length="0" type="image/png"/><dc:creator>bradluffy</dc:creator></item></channel></rss>