[{"data":1,"prerenderedAt":99},["ShallowReactive",2],{"navigation":3,"\u002Fblog\u002Fslow-design-in-fast-paced-digital-world":25,"\u002Fblog\u002Fslow-design-in-fast-paced-digital-world-surround":96},[4],{"title":5,"path":6,"stem":7,"children":8,"page":24},"Blog","\u002Fblog","blog",[9,13,17,21],{"title":10,"path":11,"stem":12},"[object Object]","\u002Fblog\u002Ffrom-mockup-to-market","blog\u002Ffrom-mockup-to-market",{"title":14,"path":15,"stem":16},"How I Keep Reusing the Same Building Blocks Across Projects","\u002Fblog\u002Fhow-i-built-my-own-design-system-from-scratch","blog\u002Fhow-i-built-my-own-design-system-from-scratch",{"title":18,"path":19,"stem":20},"Why Clear Messaging Beats Clever Copy in Cold Traffic","\u002Fblog\u002Fpsychology-of-color-in-ui-design","blog\u002Fpsychology-of-color-in-ui-design",{"title":10,"path":22,"stem":23},"\u002Fblog\u002Fslow-design-in-fast-paced-digital-world","blog\u002Fslow-design-in-fast-paced-digital-world",false,{"id":26,"title":10,"author":27,"body":28,"date":27,"description":34,"extension":81,"image":27,"meta":82,"minRead":27,"navigation":83,"path":22,"seo":84,"stem":23,"__hash__":95},"blog\u002Fblog\u002Fslow-design-in-fast-paced-digital-world.md",null,{"type":29,"value":30,"toc":75},"minimark",[31,35,38,43,46,49,59,62,66,69,72],[32,33,34],"p",{},"Speed is useful only when the result still holds together after launch.",[32,36,37],{},"That is why I prefer to automate the boring parts early: form handling, notifications, routing, status updates, and any step that would otherwise depend on someone remembering to do it manually.",[39,40,42],"h2",{"id":41},"build-the-flow-not-just-the-page","Build the flow, not just the page",[32,44,45],{},"A lot of projects stop at the visible layer. The page goes live, but the process behind it is still fragile.",[32,47,48],{},"I try to build both:",[50,51,52,56],"ol",{},[53,54,55],"li",{},"The interface the user sees",[53,57,58],{},"The automation that moves the lead or request forward",[32,60,61],{},"When those two layers are aligned, the project becomes easier to maintain.",[39,63,65],{"id":64},"keep-the-handoff-simple","Keep the handoff simple",[32,67,68],{},"The best automation is the one another person can understand quickly.",[32,70,71],{},"That means clear field names, predictable steps, and a final result that is easy to check. If a workflow needs a long explanation, it is probably too complicated.",[32,73,74],{},"Fast delivery is good. Fast delivery that survives real usage is better.",{"title":76,"searchDepth":77,"depth":77,"links":78},"",2,[79,80],{"id":41,"depth":77,"text":42},{"id":64,"depth":77,"text":65},"md",{},true,{"title":85,"description":34},{"Automation First":86,"description":87,"date":88,"image":89,"minRead":90,"author":91},"Keeping Projects Fast Without Making Them Fragile","The fastest builds are the ones that remove repeat work early and keep the handoff simple.","2025-03-01","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1516321497487-e288fb19713f?auto=format&fit=crop&w=1470&q=80",7,{"name":92,"avatar":93},"Leo Bortoluzzi",{"src":94,"alt":92},"\u002Fprofile.webp","Rfi-rEWos5m5GK0_qgX5n9yUH4jra5zo5JLBPPpatlE",[97,27],{"title":18,"path":19,"stem":20,"description":98,"children":-1},"Cold traffic needs one clear promise, one clear action, and a short path from ad to result.",1776914398068]