[{"data":1,"prerenderedAt":284},["ShallowReactive",2],{"case-studies":3},[4,106,190],{"id":5,"title":6,"body":7,"description":82,"diagram":88,"extension":89,"impact":90,"impactLabel":91,"meta":92,"navigation":93,"order":94,"path":95,"problem":96,"seo":97,"solution":98,"stem":99,"tags":100,"__hash__":105},"caseStudies\u002Fcase-studies\u002F1.lead-intake-automation.md","Lead Intake Automation for Microsoft Dynamics 365",{"type":8,"value":9,"toc":81},"minimark",[10,15,19,25,41,45,48,51,55],[11,12,14],"h2",{"id":13},"the-problem","The Problem",[16,17,18],"p",{},"A company working with three external call centers relied on manual, end-of-day email submissions to enter leads into Microsoft Dynamics 365. Every lead required a human to read the email, manually create a record, assign it to the right department, and validate the data — a process prone to delays, inconsistencies, and data loss.",[16,20,21],{},[22,23,24],"strong",{},"Core constraints:",[26,27,28,32,35,38],"ul",{},[29,30,31],"li",{},"No direct system access for external call centers",[29,33,34],{},"No budget for additional CRM licenses",[29,36,37],{},"Data inconsistencies across three different submission formats",[29,39,40],{},"Operational overhead growing with volume",[11,42,44],{"id":43},"the-solution","The Solution",[16,46,47],{},"I designed and built a custom lead intake application that sits between the external teams and MSD365 — eliminating manual entry entirely.",[16,49,50],{},"The system includes a standardized intake form for call centers, a validation layer that checks for required fields and duplicate leads, and automated routing logic that assigns leads to the correct department and entity in Dynamics based on configurable rules.",[11,52,54],{"id":53},"impact","Impact",[26,56,57,63,69,75],{},[29,58,59,62],{},[22,60,61],{},"45% reduction"," in lead assignment time",[29,64,65,68],{},[22,66,67],{},"Zero manual entry"," for 300+ weekly leads",[29,70,71,74],{},[22,72,73],{},"Consistent data quality"," across all three external teams",[29,76,77,80],{},[22,78,79],{},"Scalable"," to additional call centers with no architectural changes",{"title":82,"searchDepth":83,"depth":83,"links":84},"",2,[85,86,87],{"id":13,"depth":83,"text":14},{"id":43,"depth":83,"text":44},{"id":53,"depth":83,"text":54},"workflow","md","+45%","Faster Lead Assignment",{},true,1,"\u002Fcase-studies\u002Flead-intake-automation","Three external call centers submitted leads through end-of-day email batches. Manual CRM entry created delays, inconsistent data, and no scalability path.",{"title":6,"description":82},"Custom intake solution with automated lead routing, validation layer, and deep MSD365 integration — supporting multiple entities without additional CRM licenses.","case-studies\u002F1.lead-intake-automation",[101,102,103,104],"CRM","Automation","MSD365","Power Platform","9-J3bB07gd6_xE3Gj_oY84ELOKzUpQhjT3nRlO-wRVc",{"id":107,"title":108,"body":109,"description":82,"diagram":176,"extension":89,"impact":151,"impactLabel":177,"meta":178,"navigation":93,"order":83,"path":179,"problem":180,"seo":181,"solution":182,"stem":183,"tags":184,"__hash__":189},"caseStudies\u002Fcase-studies\u002F2.ux-conversion-optimization.md","Behavioral UX & Conversion Optimization",{"type":8,"value":110,"toc":171},[111,115,118,121,125,131,137,143,145],[11,112,114],{"id":113},"the-challenge","The Challenge",[16,116,117],{},"Optimizing conversion rates through conventional UX improvements had plateaued. The interface was clean, the flow was logical — yet users were still dropping off at key decision points.",[16,119,120],{},"The real problem wasn't the UI. It was a mismatch between the experience design and how humans actually make decisions under uncertainty.",[11,122,124],{"id":123},"counterintuitive-decisions-that-worked","Counterintuitive Decisions That Worked",[16,126,127,130],{},[22,128,129],{},"Adding friction increased conversions."," A confirmation step before a key action reduced impulsive drop-offs and increased completion rates by making users feel more in control and committed.",[16,132,133,136],{},[22,134,135],{},"Reducing choices increased engagement."," Presenting three options instead of seven eliminated decision paralysis. Users moved forward faster and felt more satisfied with their selection.",[16,138,139,142],{},[22,140,141],{},"Progressive disclosure improved usability."," Hiding advanced options behind a secondary reveal reduced cognitive load for new users while keeping power users satisfied — without removing functionality.",[11,144,54],{"id":53},[26,146,147,153,159,165],{},[29,148,149,152],{},[22,150,151],{},"+32%"," conversion rate improvement across key flows",[29,154,155,158],{},[22,156,157],{},"Reduced drop-off"," at decision-critical moments",[29,160,161,164],{},[22,162,163],{},"Higher user satisfaction scores"," post-interaction",[29,166,167,170],{},[22,168,169],{},"Framework documented"," for ongoing design decisions",{"title":82,"searchDepth":83,"depth":83,"links":172},[173,174,175],{"id":113,"depth":83,"text":114},{"id":123,"depth":83,"text":124},{"id":53,"depth":83,"text":54},"ux","Conversion Rate",{},"\u002Fcase-studies\u002Fux-conversion-optimization","Standard UX improvements weren't moving the needle. The challenge was identifying counterintuitive psychological levers that would genuinely change user behavior.",{"title":108,"description":82},"Applied behavioral psychology principles — strategic friction, progressive disclosure, and choice reduction — to create intentional experiences that guided users toward better outcomes.","case-studies\u002F2.ux-conversion-optimization",[185,186,187,188],"UX Psychology","Product Thinking","Conversion","Behavioral Design","LxcxPlw-B5_eQmYOQy6wneJdBXgDXgnLtN--doqD8vg",{"id":191,"title":192,"body":193,"description":82,"diagram":268,"extension":89,"impact":269,"impactLabel":270,"meta":271,"navigation":93,"order":272,"path":273,"problem":274,"seo":275,"solution":276,"stem":277,"tags":278,"__hash__":283},"caseStudies\u002Fcase-studies\u002F3.building-with-ai.md","Building With AI: My Workflow Advantage",{"type":8,"value":194,"toc":262},[195,199,202,205,209,215,221,227,231,234,236],[11,196,198],{"id":197},"the-insight","The Insight",[16,200,201],{},"AI tools work best when they have a defined role — not when they're used interchangeably for everything.",[16,203,204],{},"I designed a three-stage workflow where each AI tool operates in its area of strength, creating a pipeline from raw idea to shipped solution.",[11,206,208],{"id":207},"the-workflow","The Workflow",[16,210,211,214],{},[22,212,213],{},"ChatGPT → Strategy and Ideation","\nUsed for high-level thinking: problem framing, audience analysis, content strategy, and decision structuring. The goal is clarity before execution.",[16,216,217,220],{},[22,218,219],{},"Stitch → Visual Exploration","\nUsed for rapid visual prototyping: exploring design directions, layout concepts, and visual references before committing to implementation.",[16,222,223,226],{},[22,224,225],{},"Claude → Implementation and Iteration","\nUsed for building: writing code, refining logic, iterating on implementations, and maintaining quality across complex multi-step tasks.",[11,228,230],{"id":229},"why-it-works","Why It Works",[16,232,233],{},"The separation of cognitive modes — thinking, seeing, building — prevents context switching overhead and keeps each tool focused on what it does best. The result is a repeatable pipeline that dramatically compresses execution time without sacrificing quality.",[11,235,54],{"id":53},[26,237,238,244,250,256],{},[29,239,240,243],{},[22,241,242],{},"3× faster"," idea-to-implementation cycles",[29,245,246,249],{},[22,247,248],{},"Higher quality output"," through focused tool use",[29,251,252,255],{},[22,253,254],{},"Documented and repeatable"," system for any new project",[29,257,258,261],{},[22,259,260],{},"Continuously improving"," as models evolve",{"title":82,"searchDepth":83,"depth":83,"links":263},[264,265,266,267],{"id":197,"depth":83,"text":198},{"id":207,"depth":83,"text":208},{"id":229,"depth":83,"text":230},{"id":53,"depth":83,"text":54},"ai","3×","Execution Speed",{},3,"\u002Fcase-studies\u002Fbuilding-with-ai","Complex projects required moving between strategy, visual exploration, and implementation — each phase traditionally siloed in different tools and mindsets.",{"title":192,"description":82},"Built a personal AI-assisted workflow that assigns each tool a specific cognitive role, enabling faster ideation-to-execution cycles without sacrificing quality.","case-studies\u002F3.building-with-ai",[279,280,281,282],"AI-Assisted","Workflow","Productivity","Systems Thinking","E9UDZ-ocxu4BEQxaKrIO4Lp9Og7SxfsZp6rZmXchYfY",1780402736483]