
AI did the legwork and the audits. Every pick was mine.
Planned and ran interviews with travelers who plan their own trips, and set the questions that mattered
AIMapped my assumptions and turned them into interview questions, transcribed the talks, and pulled out more than 130 observations in minutes. I checked every one against the transcript and kept 99. It also researched competitors and similar problems in other fields.
Chose the need and the problem to design for, and cut the insights down to the strong ones by hand
AIGrouped the observations into themes and drafted a need statement. It wrote five problem statements from five different angles at once, then audited them. When I changed direction, it rebuilt the whole synthesis, including the persona, in a day.
Chose the concept and decided what is in scope
AIGenerated five concepts from five angles in parallel and rated each for desirability, viability and feasibility, with evidence. It mapped the user flow, then hunted for dead ends, missing steps and edge cases. It also built a prototype so I could test whether AI-driven research is good enough to rely on.
Directed the design, reviewed every screen and signed off the documents
AIBuilt the prototype in Claude Design, wrote the handoff and built the app with Claude Code. It also checked 18 project documents against their sources before I approved them.
Frustrations with Google MyMaps
After using Google's MyMaps to plan all my trip for years, i was very frustrated with its limitations. So i wanted to build my own app that lifts the limitations and adds AI-Powered research capabilities.
The maximum number of layers for this map has been reached.
OKLimits for layers and pins per route
In MyMaps there are only 10 layers available to manage all your pins, routes and collections, which quickly run out. It's not possible to plan trips longer than a week without applying some workarounds.
Start southwest on 小松拡幅/琵琶湖西縦貫道路/国道161号
Take the Wani IC exit
Turn left towards 県道311号
Turn right onto 県道311号
Turn right onto レインボーロード/国道477号
Turn left onto 国道367号
Start southwest on 小松拡幅/琵琶湖西縦貫道路/国道161号
Take the Wani IC exit
Turn left towards 県道311号
Turn right onto 県道311号
Turn right onto レインボーロード/国道477号
Turn left onto 国道367号
Drive times are buried in turn-by-turn directions
The time for a leg sits between cryptic driving instructions. With routes for more than one day squeezed into one layer, the relevant times had to be extracted and added up manually.

Pictures break over time
Photos on a pin only link to outside sources. When a link changes, the picture is gone, and the pin no longer tells me what it was. In a test on a two-year-old map, more than a third of the images had disappeared.
No research, so every find comes from elsewhere
MyMaps can't search for places. Every find had to come in from other apps and be added by hand, one pin at a time.
User interviews and building the live app started in parallel
Along with the traditional user interviews I started building the app itself, beginning with a brain-dumped concept of what an MVP needs. Its first versions tested the riskiest assumptions: how precisely free services place pins, how good the research results are and how good the image sources are. I wrote down what I learned. Later I combined the interview insights, those learnings and the initial concept into a new concept. The clickable prototype grew out of it, and the app now catches up with what the prototype added.
Testing the feasibility of the concept live
In the first version of the app I tested the riskiest assumptions: how precisely free services place pins, how good the quality of the built-in research could be and where to source the best images.
Research & Discovery
I interviewed travelers aged 40 to 56 who plan their own trips, and I treated my own interviews as one more participant. They covered how people find places, how they decide, and where their tools get in the way. The results hold for experienced, self-organized planners only. In parallel I built a test app. Its main job was to investigate technical limits: how good built-in travel research is, whether every pin can get exact coordinates, and whether good photos can be found.
The insight
Planning is a funnel from many finds to a shortlist to day-sized routes, and each step lives in a different tool.
What was made and why
I built Vayo along that funnel: find, shortlist, plan the days.
Finding: free questions instead of fixed categories
I started with a batch tool that searches fixed categories by region. On paper it made sense. In the test app I saw that choosing from fixed categories can make you miss good spots, and in the interviews nobody described searching from a fixed list. So I built the research as free questions to the AI. The results land on the map right away, and I decide on each one.
Shortlisting: keep or skip first, ratings later
In the interviews, one traveler said he wanted to go through spots quickly, like swiping: like or dislike. So every find gets a fast keep or skip first, and ratings come later, once a shortlist exists. The alternative was rating every place the moment it appeared. Rating pins at all is a big step up from MyMaps, which has nothing like it, and it turns the kept finds into a shortlist I can build days from.
Planning the days: from a list of stops to a day that adds up
In MyMaps, a route was a list of stops. In Vayo, drive times between places show instantly and add up per day and for the whole trip. I added a start time for each day, so I can see whether a day can be done while the sun is still up. For that I needed the time spent at each place. Google's API has it, but it costs extra. Then I had the idea to ask the AI that was already connected to the app. It finds the time at no extra cost, and I can still change it.
Outcome
Planning a trip like this used to take me 2 to 3 months. With Vayo it took 2 to 3 weeks, and I planned a full 4-week trip with it. So far only I have used it, so I can't yet say how it works for anyone else.
If I did it again, I would start discovery from what I already knew. I had years of my own trips and years of conversations with friends about how they plan, and none of that went into the research. I treated the topic as unknown, so the discovery phase repeated things I could have started from.
