[{"data":1,"prerenderedAt":241},["ShallowReactive",2],{"blog-why-conversations-dont-fit-into-trees":3},{"id":4,"title":5,"body":6,"description":12,"extension":230,"meta":231,"navigation":235,"path":236,"seo":237,"sitemap":238,"stem":239,"__hash__":240},"blog\u002Fblog\u002Fwhy-conversations-dont-fit-into-trees.md","Why Conversations Don’t Fit Into Trees",{"type":7,"value":8,"toc":215},"minimark",[9,13,19,24,27,30,46,54,58,61,66,69,75,79,82,85,88,92,95,102,106,109,116,120,128,135,139,146,157,162,166,169,191,194,199,208],[10,11,12],"p",{},"Many chatbot builders still treat conversations like decision trees. This may seem logical at first but it quickly leads to inflexible designs, messy edge cases, and unnecessary programming.",[14,15,16],"blockquote",{},[10,17,18],{},"Real conversations are not trees. They’re networks. And that changes everything.",[20,21,23],"h2",{"id":22},"why-trees-fall-short","Why Trees Fall Short",[10,25,26],{},"You’ve probably seen it before: a chatbot builder that uses a tree-like layout to map out conversations. It looks clean... until it doesn’t. Real conversations don’t follow such strict branching logic.",[10,28,29],{},"In reality, they:",[31,32,33,37,40,43],"ul",{},[34,35,36],"li",{},"Loop back.",[34,38,39],{},"Converge at conclusions.",[34,41,42],{},"Depend on multiple conditions.",[34,44,45],{},"Reuse earlier answers.",[10,47,48,49,53],{},"This isn't just a technical issue - it's a ",[50,51,52],"strong",{},"modeling problem",".",[20,55,57],{"id":56},"five-patterns-that-may-or-may-not-fit-into-a-tree","Five Patterns That May (or May Not) Fit Into a Tree",[10,59,60],{},"Let’s look at common conversational patterns and where tree structures begin to fail.",[62,63,65],"h3",{"id":64},"_1-sequential-question-chains","1. Sequential Question Chains",[10,67,68],{},"Simple back-to-back questions. Great for onboarding or form-filling.",[10,70,71,74],{},[50,72,73],{},"Trees can handle this."," No logic needed.",[62,76,78],{"id":77},"_2-classic-tree-branches","2. Classic Tree Branches",[10,80,81],{},"This is where many builders stop. A question leads to answers, each branching out into new paths.",[10,83,84],{},"But what if questions should come back together? Or what if later questions depend on multiple earlier answers?",[10,86,87],{},"Trees can’t do that well.",[62,89,91],{"id":90},"_3-diamond-shapes-merging-paths","3. Diamond Shapes (Merging Paths)",[10,93,94],{},"Multiple branches converging into a shared conclusion - like forming a diagnosis or summarizing intent.",[10,96,97,98,101],{},"This ",[50,99,100],{},"requires a network",", not a tree. In trees, merged logic often means messy hacks or hidden condition checks.",[62,103,105],{"id":104},"_4-complex-conversation-networks","4. Complex Conversation Networks",[10,107,108],{},"By combining chains, trees, diamonds, and loops, you get flexible conversation flows that mirror real-life interactions.",[10,110,111,112,115],{},"This is what ",[50,113,114],{},"Wanderer"," is built for.",[62,117,119],{"id":118},"_5-deep-contextual-conclusions","5. Deep Contextual Conclusions",[10,121,122,123,127],{},"Sometimes outcomes depend on ",[124,125,126],"em",{},"several"," conditions across different branches. This can’t be represented cleanly in a tree.",[10,129,130,131,134],{},"Instead, it needs ",[50,132,133],{},"graph-based logic",", where multiple edges feed into a single conclusion node with clear, testable conditions.",[20,136,138],{"id":137},"the-tree-is-only-the-path-not-the-map","The Tree Is Only the Path, Not the Map",[10,140,141,142,145],{},"Here’s the trick: when a conversation happens in real time, the path a user takes ",[124,143,144],{},"can"," look like a tree.",[10,147,148,149,152,153,156],{},"But the ",[50,150,151],{},"system"," underneath should still be a ",[50,154,155],{},"network"," with all paths, logic gates, and alternatives in place.",[14,158,159],{},[10,160,161],{},"A user’s journey is a tree. But your logic should live in a network.",[20,163,165],{"id":164},"why-wanderer-is-built-as-a-graph","Why Wanderer Is Built as a Graph",[10,167,168],{},"Wanderer embraces the full complexity of conversations:",[31,170,171,178,181,188],{},[34,172,173,174,177],{},"Logic lives in ",[50,175,176],{},"edges",", not hidden in code.",[34,179,180],{},"You can combine patterns freely: trees, diamonds, loops.",[34,182,183,184,187],{},"The flow remains ",[50,185,186],{},"visual, transparent, and editable"," at all times.",[34,189,190],{},"Conversations evolve dynamically with real-time state logic.",[10,192,193],{},"Whether you're building a chatbot, survey, or interactive guide your users deserve more than a decision tree.",[10,195,196],{},[50,197,198],{},"Let’s give them a real conversation.",[10,200,201],{},[202,203,207],"a",{"href":204,"rel":205},"https:\u002F\u002Fwanderer-flow.de\u002Fbuilder",[206],"nofollow","Start the Builder",[10,209,210,211],{},"Title image: ",[202,212,213],{"href":213,"rel":214},"https:\u002F\u002Fpixabay.com\u002Fde\u002Fphotos\u002Fbaum-natur-holz-kahler-baum-stamm-3097419\u002F",[206],{"title":216,"searchDepth":217,"depth":217,"links":218},"",2,[219,220,228,229],{"id":22,"depth":217,"text":23},{"id":56,"depth":217,"text":57,"children":221},[222,224,225,226,227],{"id":64,"depth":223,"text":65},3,{"id":77,"depth":223,"text":78},{"id":90,"depth":223,"text":91},{"id":104,"depth":223,"text":105},{"id":118,"depth":223,"text":119},{"id":137,"depth":217,"text":138},{"id":164,"depth":217,"text":165},"md",{"date":232,"author":233,"headerImage":234},"2025-04-02","Chris","\u002Fimages\u002Fblog\u002Ftree.jpg",true,"\u002Fblog\u002Fwhy-conversations-dont-fit-into-trees",{"title":5,"description":12},{"loc":236},"blog\u002Fwhy-conversations-dont-fit-into-trees","RHWcutyREx07NxLrEwSDC16W4EpJiHFkX2bjy5ykeXY",1786889213828]