All Posts

This engagement focused on implementing a structured Smartsheet system to support mentor tracking, cohort management, and program reporting.

What began as a set of operational trackers had evolved into a multi-sheet Smartsheet environment supporting intake, consultations tracking, treatment, and compliance oversight for a behavioral health organization with under 100 staff members.

There is a difference between building sheets and designing a system. A strong Smartsheet implementation is not about volume; it's about structure.

Before You Build in Smartsheet, Build Clarity Understanding the Importance of Clarity I’ve worked with many teams eager to build in Smartsheet. They often have a process that feels messy, a list of frustrations, and a vision for something smoother. So, they start creating sheets, linking cells, adding forms, and naming dashboards. However, halfway through the build, the friction begins to show. The sheet logic becomes patchy. The team isn’t sure who is responsible for updatin

If you’ve ever opened your Smartsheet setup and thought “this feels like a lot,” you’re not alone. Many teams assume that when Smartsheet starts to feel heavy, confusing, or hard to maintain, the system has outgrown its usefulness. In reality, most systems don’t become unusable because they’re too complex. They become unusable because they’re doing too much at once . How “Helpful” Systems Slowly Turn Into Messy Ones Almost every messy Smartsheet system starts with good inten

Most Smartsheet environments do not fail because the tool is wrong. They fail because the system was never designed with enough clarity. When teams ask me to audit their Smartsheet environment, they often expect a technical review. They assume I am going to point out broken formulas, messy sheets, or automations that misfire. Those things show up. But they are never the root problem. An audit is really a systems conversation. It tells me how the work flows, where decisions br