Streamlining Consulting Workflows

How we saved 10+ hours weekly by giving finance a simple interface. Our finance team was processing invoices the same way for years: 1. Email attachments → 2. Manual download → 3. Print → 4. Physical signature → 5. Scan → 6. Manual data entry The entire cycle took 3-5 days. The request to "build a proper approval system" kept getting deprioritized—it felt like a multi-month project. We reframed the problem: We didn't need a complex system. We just needed to connect two things: the data from our accounting software's API and a simple list where the right people could click "Approve" or "Reject." What actually got built: • A single-page app that pulls unpaid invoices automatically • Logic that routes invoices over $5k to directors, others to managers • A comment field for rejections • A basic audit log showing who approved what and when What changed: ✅ Approvals now happen in under 24 hours ✅ The finance team stopped chasing paper trails ✅ Vendors get paid faster ✅ Every decision is logged automatically The takeaway: Sometimes "digital transformation" isn't about big platforms. It's about giving a team one less PDF to manage by building a simple, focused tool that sits on top of the data they already use. What's the most stubborn, repetitive task in your team's workflow? Often the highest-impact tools are the smallest ones that remove a single point of friction. https://uibakery.io/ #ProcessAutomation #FinanceTech #OperationalEfficiency #DigitalTransformation

🎤 “I promise you’ll never find another like me” - “ME” by Taylor Swift 📕 Let's talk about how to move down-market... 📈 In the latest G2 grid for #CustomerSuccess software, Gainsight is far and away the furthest up and to the right - both in terms of market share as well as customer satisfaction. 🏆 This has been true for a while, but now we are also a clear leader (along with our friends ChurnZero) in mid-market CS software (50-1000 employees) - see below. How did we make progress in the mid-market? Here’s what we learned… 💿 Product: Of course, it always starts here. Mid-market leaders want to start fast. But they also want to scale and not have to switch platforms as they grow. So we created templates in our product for the most common scenarios our clients encounter (e.g., NPS followup, renewal alerts). Since companies of all sizes change rapidly, we also put more power in the hands of end users - to create reports, personalize their workspace and more. 💲 Pricing: Enterprise pricing is always complex; but mid-market companies want clarity - so we moved to very simple, competitive and transparent pricing model. 📣 Marketing: Part of simplifying is simplifying the message. Our CMO Scott S. and his team drove a whole new approach. They cut down our slide deck significantly. They created a dedicated site for our Essentials offering. And they focused more on actual customer evidence (hence G2!) 💰 Sales: Mid-market companies want to move fast - even in the sales process. So we created a streamlined workflow to reduce the number of hops in our go-to-market and pushed prospects into our trial environment that we call Joy Ride. ⏱️ Time-to-value: Time-to-value matters for all companies. But for mid-sized firms, speedy deployments are essential. At the same time, companies don’t necessarily have budget for a a full Professional Services engagement. So we designed a rapid onboarding to help customers go live in 2-4 weeks at a very affordable price point. 🥇 Customer Success: Best practices don’t stop in implementation. Indeed, clients come to SaaS vendors these days for ongoing advice. We created an “accelerator” program to bring new clients into cohort groups with similarly-sized companies to learn from CS experts in small virtual sessions. In parallel, we included a Customer Success Solutions Consultant to eliminate the need for a Gainsight Administrator and instead offer on-demand configuration, guided by a CS leader or Sales Operations professional. The results: 📈 300+ clients are now using Gainsight Essentials 💻 Most have no dedicated Gainsight Administrator, though they all plan to hire one as they scale. ❤️ These clients now report NPS between 50 and 70 👏🏾 And of course, the G2 results below Moving down market isn’t easy but it’s incredibly rewarding when it happens. How about you? What have you learned if you moved from a focus on enterprise to targeting both enterprise and mid-market in your company? 

RFP responses can be a real challenge. They’re often slow and inconsistent due to scattered knowledge and manual processes. This was the case for a global consultancy that wanted to speed up how it brought its offerings to market. Sales teams struggled to access past proposals, relevant case studies, and client-specific context. This customer was an early Glean Agent adopter, and we’re thankful for their feedback along the journey. To address this challenge, they deployed a suite of Glean agents. The goal was to unify content discovery and streamline proposal workflows, pulling from their company knowledge bases, CRM systems, and external research to support end-to-end RFP generation. This was paired with a methodical approach to enablement and adoption. Some examples of agents they built: • A Client Need Triage agent that maps client requirements to standard service offerings • A Research agent to pull together industry and company-specific insights • A Historian agent to surface past engagements and account activity right from the CRM • A Proposal Helper agent to accelerate proposal creation with standardized, offering-aligned drafts This foundation delivered real business value: • Proposal development time dropped from 4 weeks to just a few hours. That’s a 97% productivity gain. • A heuristic metric of deflecting over $150K if a single point enablement Saas solution was chosen. By embedding agents directly into the sales workflow, the consultancy improved both speed and precision in proposal development. Now, they’re looking to apply the same agent-driven approach to other parts of the business, like managed services and engineering, to bring that same efficiency and intelligence everywhere.

Don’t Automate Complexity... Simplify and Error-Proof Instead When problems arise, it’s tempting to think automation is the magic fix. But automating a broken or complex process just means you’re speeding up the production of errors. The smarter approach? Simplify the process and error-proof it (Poka Yoke) before thinking about automation. Here’s why simplification often beats automation and how you can apply it. Why You Should Simplify Before Automating: 1️⃣ Faster, Cheaper Improvements Simplifying a process through standardization and removing unnecessary steps often solves problems more quickly and at a lower cost than automation. 2️⃣ Avoid Automating Waste If your process is full of waste (like waiting, overprocessing, or rework), automating it only speeds up inefficiency. Fix the process first, then think about automation. 3️⃣ Built-In Error Proofing With Poka Yoke solutions (like jigs, fixtures, or guides), you can design processes to prevent errors from happening in the first place—without needing expensive sensors or software. 4️⃣ Flexibility and Adaptability Simplified processes are easier to adjust and improve, while automated systems can be rigid and costly to change once implemented. How to Simplify and Error-Proof a Process: 🔍 Map the Current Workflow: Identify unnecessary steps, bottlenecks, and areas prone to errors. ✂️ Eliminate Waste: Remove any steps that don’t add value to the product or service. 📋 Standardize Work: Create clear, repeatable instructions that everyone can follow. 🔧 Introduce Poka Yoke: Physical Error-Proofing: Use jigs, fixtures, or alignment guides to prevent incorrect assembly. Visual Cues: Use color-coded labels or visual templates to guide operators. Sensors or Alarms: Only when needed, use low-cost technology to detect errors in real time. Example of Simplification and Poka Yoke in Action: A warehouse team was dealing with frequent errors when picking products for orders. Instead of implementing a costly automated picking system, they: 1. Introduced a color-coded bin system (Poka Yoke) to help operators select the correct items. 2. Simplified the picking route to reduce unnecessary walking and waiting time. Result: Picking errors dropped by 80%, and productivity increased by 15%—all without expensive automation. When to Consider Automation: Once the process is simplified and stabilized with minimal variation, automation can enhance speed and efficiency. But it should support an optimized process, not mask its problems.

You know that moment where one missed message snowballs into a full-blown disaster? I run a marketing agency and I handle too many clients, meet a lot of deadlines and manage a lot of urgent things. It used to be really difficult until I stopped relying on memory and started building systems. So here's how I don’t lose my mind every week- 1. Calendars = Sanity I don’t hope I remember meetings, I calendar them like my life depends on it.  Client calls, brainstorm meetings, weekly reviews everything has its own time block. That way I can plan my week effectively. 2. Task breakdown Every project starts with a crystal-clear workflow. We’ve built workflows for each client, creative → review → client feedback → final delivery. And each task has an owner, and a deadline. Nobody’s left guessing. Nobody’s stuck waiting. 3. Client calls. We do a dedicated check-in every week or biweekly.  With clear agendas, updates and next steps. Clients love it because they know exactly where things stand. 4. WhatsApp is our heartbeat No, it’s not fancy. But it’s fast. From sharing urgent client feedback to dropping quick voice notes when I’m too tired to type, I do it all on whatsapp. Each client has a pinned group. It’s quick and convenient. 5. The good old notes app Ideas, hooks, reels, client feedback during a Zoom call that random “oh, this idea would work for their next launch” All of it gets dumped straight into Notes. It’s my second brain. Systems = Less drama and more focus With these in place, I’m not firefighting every day. I’m thinking ahead, building and scaling. So, if you're feeling overwhelmed running your business, it’s not because you’re not capable. It’s probably because your systems aren’t in place. 

9 ways to optimize your RAG Apps directly from AWS engineers! Most RAG applications fail because of poor document structure, not model limitations. Here's what AWS discovered after testing thousands of enterprise RAG deployments: 1. Use proper headings and subheadings • Improves document readability and navigation • Helps RAG models understand content structure • Enables better information extraction 2. Keep numbering sequential  • Maintain proper numbering without skipping • Avoids confusion in listed content • Ensures clarity and coherence 3. Add transitions between list items • Use phrases like "After completing step 2, do..." • Guides the LLM through your content flow • Connects ideas for better comprehension 4. Replace tables with bulleted lists • Use multi-level bullets or flat-level syntax • LLMs digest linear information better • Improves structured data processing 5. Preprocess graphical information • Reduce image resolution to save tokens • Remove redundant visual content • Add text descriptions of graphics 6. Add session starters for common queries • Include phrases like "If you are looking to order software..." • Creates high semantic matching • Helps LLM construct cohesive responses 7. Include summaries after each section • Add brief content overviews under headings • Increases semantic coverage and reinforces key points • Improves similarity search accuracy 8. Define abbreviations and set context • Explain company-specific terminology • Set proper context for enterprise documents • Prevents hallucinations and improves accuracy 9. Break large documents into smaller pieces • Divide complex documents by subtopic • Create self-contained documents with clear titles • Improves indexing and tagging efficiency The biggest insight? RAG performance depends more on how you prepare your data than which model you choose. Have you optimized your document structure for RAG?

If delegation is supposed to create freedom, why does it so often create frustration? According to Harvard Business Review, The biggest delegation failures don’t come from too much or too little autonomy — they come from unclear expectations and mismatched levels of guidance, which erode trust and slow performance over time. 🔗 HBR — Why Delegation Fails https://rb.gy/qper2e That’s the real delegation paradox. Most managers think delegation is about letting go. In reality, it’s about staying appropriately involved. I see this weekly in executive coaching. Leaders delegate a task…Then disappear. Assuming autonomy equals empowerment. What teams experience instead is ambiguity. No clarity on: ↳ What “good��� looks like ↳ How decisions should be made ↳ When to check in — or when not to And ambiguity doesn’t feel like freedom. It feels like risk. Here’s the reframe most leaders miss: Delegation isn’t a binary choice between micromanagement and hands-off leadership. It’s a dynamic agreement. The best leaders don’t ask: “Should I step in or step back?” They ask: “What level of thinking, judgment, and support does this person need right now?” That level changes: • By task • By experience • By confidence • By context Great delegation adapts. Poor delegation assumes. Here’s what I encourage you to try next: 🔹 Name the level of autonomy explicitly. Say: “Here’s where I want you to decide independently — and here’s where I want visibility.” 🔹 Clarify the thinking, not just the task. Explain how decisions should be made, not just what needs to be done. 🔹 Use check-ins to reduce anxiety, not control. Regular touchpoints signal support — not mistrust — when expectations are clear. Delegation done well doesn’t just move work. It develops judgment. And that’s the real goal. Because in the AI era, tools can distribute tasks instantly. Only leaders can grow thinkers. And because in the AI era, tools don’t create sustainable performance. Human Intelligence does. Coaching can help; let's chat. #criticalthinking #executivecoaching #leadership

Let's be honest: extensive cross-team coordination is often a symptom of a larger problem, not an inevitable challenge that needs solving. When teams spend more time in alignment than on building, it's time to reconsider your organizational design. Conway's Law tells us that our systems inevitably mirror our communication structures. When I see teams drowning in coordination overhead, I look at these structural factors: - Team boundaries that cut across frequent workflows: If a single user journey requires six different teams to coordinate, your org structure might be optimized for technical specialization at the expense of delivery flow. - Mismatched team autonomy and system architecture: Microservices architecture with monolithic teams (or vice versa) creates natural friction points that no amount of coordination rituals can fully resolve. - Implicit dependencies that become visible too late: Teams discover they're blocking each other only during integration, indicating boundaries were drawn without understanding the full system dynamics. Rather than adding more coordination mechanisms, consider these structural approaches: - Domain-oriented teams over technology-oriented teams: Align team boundaries with business domains rather than technical layers to reduce cross-team handoffs. - Team topologies that acknowledge different types of teams: Platform teams, enabling teams, stream-aligned teams, and complicated subsystem teams each have different alignment needs. - Deliberate discovery of dependencies: Map the invisible structures in your organization before drawing team boundaries, not after. Dependencies are inevitable and systems are increasingly interconnected, so some cross-team alignment will always be necessary. When structural changes aren't immediately possible, here's what I've learned works to keep things on the right track: 1️⃣ Shared mental models matter more than shared documentation. When teams understand not just what other teams are building, but why and how it fits into the bigger picture, collaboration becomes fluid rather than forced. 2️⃣ Interface-first development creates clear contracts between systems, allowing teams to work autonomously while maintaining confidence in integration. 3️⃣ Regular alignment rituals prevent drift. Monthly tech radar sessions, quarterly architecture reviews, and cross-team demonstrations create the rhythm of alignment. 4️⃣ Technical decisions need business context. When engineers understand user and business outcomes, they make better architectural choices that transcend team boundaries. 5️⃣ Optimize for psychological safety across teams. The ability to raise concerns outside your immediate team hierarchy is what prevents organizational blind spots. The best engineering leaders recognize that excessive coordination is a tax on productivity. You can work to improve coordination, or you can work to reduce the need for coordination in the first place.

𝗪𝗵𝘆 𝗱𝗼 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗘𝗥𝗣 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹? 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘁𝗿𝗲𝗮𝘁 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝗰𝗵, not the business transformation it truly is. Listening to my network, there seems to be a rush to complete ERP migrations, as fast as possible, with SAP S/4HANA plans driving most of it. But an ERP system is more than just an IT upgrade. It’s a chance to redesign how your business operates and build a solution architecture that supports agility and innovation. While necessary, these migrations often become redundant without proper alignment to business goals. Something, I've seen happen! Here some get rights to consider: ◉ 𝗔𝗹𝗶𝗴𝗻 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗮𝗻𝗱 𝘁𝗲𝗰𝗵 𝗴𝗼𝗮𝗹𝘀 Ensure that IT and business leaders are on the same page. ERP systems serve broader business objectives, such as innovation, improving procurement strategies, and enhancing supplier relationships. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗼𝗼𝗹𝘀. Instead of getting caught up in the technology itself, be clear about the business benefits you'd like to achieve. New ERP functionality can be of support to achieve goals like efficiency, cost reduction, and agility. ◉ 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 𝗮𝗻𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 Don't just migrate complex, outdated processes but streamline them end-to-end. Reevaluate processes for efficiency and desired outcomes. ◉ 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗶𝗻 𝘁𝗿𝗮𝗶𝗻𝗶𝗻𝗴 ERP migrations often fail due to poor user adoption. Beyond training, invest in communication & ongoing support showing the value and relevance of the system to users. ◉ 𝗜𝗻𝘃𝗼𝗹𝘃𝗲 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘁𝗲𝗮𝗺𝘀 ERP impacts every area of the business, so cross-team collaboration is essential. Involve stakeholders from finance, procurement, IT, and operations ensures the system meets everyone’s needs. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 - 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗰𝗼𝗺𝗽𝗿𝗼𝗺𝗶𝘀𝗲 An ERP system is only as good as the data it processes. Ensure that data is clean, consistent, and reliable before migration. Dirty or incomplete data is one of the biggest challenges post-go-live. ◉ 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘀𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗖𝗼𝗺𝗽𝗼𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 Choose an architecture which allows for future-proofing and integration of new features, scalability and integration. Business models evolve, and your ERP must evolve with them." ◉ 𝗦𝗲𝘁 𝗿𝗲𝗮𝗹𝗶𝘀𝘁𝗶𝗰 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲𝘀 - 𝗶𝘁'𝘀 𝗻𝗼𝘁 𝗴𝗼𝗶𝗻𝗴 𝘁𝗼 𝗯𝗲 𝗾𝘂𝗶𝗰𝗸 𝗶𝗳 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝘃𝗲 Don’t rush an implementation. ERP migrations are complex and require time to integrate properly. A phased approach allows for troubleshooting and mitigates a risk for failure. ❓Any other "get rights" i missed and you would add from your experience. #erp #businesstransformation #migration #sap4hana

Operational bottlenecks are often mistaken for minor distractions. In textiles, challenges such as machine downtime, dye-house delays, working capital spikes, or capacity mismatches between spinning and weaving are not just inconveniences. They are critical leverage points for value creation and significant professional impact. Many leaders focus on optimising every area. However, sustainable throughput comes from identifying and rigorously managing the single constraint that governs the entire system. We apply the Theory of Constraints (TOC) at RSWM to convert operational friction into performance gains. TOC shows that local efficiency can be misleading. Keeping every department busy often creates excess work-in-progress, disrupting flow, increasing costs, and delaying deliveries. Instead, we follow a disciplined process: -First, identify what sets the pace of the value chain. This may include machinery misaligned with current market needs or process challenges like low Right First Time (RFT) rates in the dye house that reduce effective capacity. -Second, exploit the constraint by precise scheduling, strengthening discipline, and improving efficiency to extract more output without immediate capital deployment. -Third, align the rest of the organisation to the bottleneck’s pace to ensure smooth material flow across departments. Fourth, elevate the constraint through capital investment or process redesign, addressing capacity mismatches or refining product lines. -Finally, repeat the cycle, since the constraint shifts as performance improves. This approach has delivered tangible results at RSWM. Addressing dye-house bottlenecks increased throughput, reduced working capital requirements, and improved EBITDA. However, constraints change over time. Market shifts, such as China’s shift from a major yarn importer to an exporter, or recent U.S. tariffs affecting demand, can pose new challenges. In response, we adapt by exploring alternative markets, leveraging domestic opportunities, or innovating products to sustain growth. Our goal is to eliminate internal friction so operational excellence drives expansion. When the market is the only constraint, the organisation is positioned to thrive. #TheoryOfConstraints #OperationalExcellence #Textiles #Leadership #RSWM