Fieldnotes offers a distinct alternative to wikis and generic chatbots by focusing on opinionated, grounded answers. The use of a structured CMS with Sanity allows for clear authoring of frameworks and processes. The semantic search powered by embeddings helps users find relevant insights quickly. However, the value depends entirely on the existing knowledge base. It is not a replacement for deep expertise but a tool to organize and retrieve the judgment of senior design leaders. The emphasis on tension and maturity adds depth that standard documentation often lacks.
Haven't used fieldnotes yet?
Ask Trustburn
What reviewers say about fieldnotes
Customers appreciate the conversational interface that feels like mentorship and the use of semantic search for precise retrieval of grounded insights. Some users note that the value depends heavily on the quality of the input data and that it requires initial setup to populate the CMS.
What does fieldnotes do?
fieldnotes is a design knowledge resource created by Stuart Wainstock that offers conversational access to fifteen years of design leadership experience.
Are there any complaints about fieldnotes?
The reviews on file do not mention specific complaints.
Post your question publicly — other visitors, and whoever manages this page, can answer. It will be visible on this page.
Want to hear about this company again? Follow it and we’ll email you when a new review appears.
Based on reviews on this page. Verify anything important with the company directly.
5 Reviews
The structured approach to design knowledge is promising, though it relies heavily on the quality of the input data.
What stands out most is how fieldnotes captures the nuance of design leadership. The concept of four fields encoding judgment—confidence, tension, maturity, and myTake—transforms dry documentation into something that feels like mentorship. Instead of just listing processes, it explains the tradeoffs and the real-world context where frameworks break down. The architecture using Next.js and Vercel ensures it is fast and accessible. It feels less like querying a database and more like having a conversation with someone who has been in the trenches for fifteen years. The ability to calibrate answers based on organizational maturity is particularly useful for scaling teams without losing the nuance of good design practice.
The integration of OpenAI embeddings with Supabase vector storage allows for precise semantic retrieval. This ensures that the conversational interface remains grounded in the actual published knowledge base rather than hallucinating details. It is a robust approach to knowledge management.
The structure of fieldnotes seems well-conceived for design teams. The distinction between frameworks and processes is clear, and the use of confidence levels helps in understanding the maturity of each insight. While it requires some initial setup to populate the CMS, the effort appears worthwhile for preserving institutional knowledge. It avoids the pitfalls of generic chatbots by grounding answers in published content, which feels reliable for serious design work.
Questions & Answers
No questions yet — be the first to ask.
Sign in to post
Your text is saved — you'll come right back to post.
or with email
Don't have an account? Create one
News & Press
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
About fieldnotes
fieldnotes is a design knowledge resource created by Stuart Wainstock that offers conversational access to fifteen years of design leadership experience. It allows users to ask questions and receive responses grounded in frameworks, processes, and insights rather than functioning as a standard search tool or wiki. The content is organized into categories including mental models, processes and steps, and opinions or convictions drawn from practical experience. The site is built on Sanity and powered by Claude.
- Website
- fieldnotes.design
- Categories
- Design
