In previous iterations of the Thinkwise GUI you could perform an action called quicksearch.
How it worked:
- Bring focus to a specific column (in the grid)
- Type what you want to search
- First match of your search gets selected/highlighted.
Can we please have this back?
Why Quicksearch is valuable (and missed)
1. Strong productivity gain for keyboard users
Quicksearch enabled fast, uninterrupted workflows:
No mouse interaction required
No modal dialogs or filter configuration
Immediate feedback while typing
For users who work with data grids all day, this shaved seconds off every lookup — which adds up quickly.
2. Ideal for exploratory and ad‑hoc searching
Quicksearch was perfect when:
You don’t know the exact value
You just want to jump to something that looks right
You don’t want to define a full filter for a one‑off check
Current alternatives (filters, column search fields) feel heavier for this use case.
3. Lower cognitive load than filtering
Quicksearch required almost no mental overhead:
Focus column
Type
First match selected
Compared to:
Opening filters
Choosing operators
Applying / clearing filters
This made it especially useful during conversations with users or while debugging data.
4. Excellent for large datasets
In grids with many rows:
Scrolling is inefficient
Sorting doesn’t always help
Filters can be overkill
Quicksearch acted as a “jump to value” mechanism, not a data‑reduction mechanism — a subtly different but very useful interaction.
5. Consistency with legacy behavior & muscle memory
Many long‑time Thinkwise users built muscle memory around this feature.
Its removal:
Breaks established workflows
Increases friction when moving to Universal UI
Makes Universal UI feel like a regression in this specific area, despite its overall improvements
6. Complementary, not a replacement, to filtering
Quicksearch didn’t replace filters — it complemented them:
Filters = structured, intentional selection
Quicksearch = fast navigation and orientation
Both serve different user intents and can coexist.