resolved
Lattice
lattice.com/performance/reviews
landed in 38msBookSlash for Lattice · HR
b/reviews.
b/goals. b/1-1.
Lattice runs reviews, OKRs, and 1:1s. The URLs to your active review cycle, your goals page, and your 1:1 agenda each get a flat name everyone on the team types.
reviews
other shortcuts you might save
b/reviewsb/goalsb/1-1b/feedback
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for Lattice, with notes on why each one survives the URL changes that break personal bookmarks.
- b/reviews
Active review cycle.
Every employee reaches it during review windows.
https://app.lattice.com/performance/reviews - b/goals
Personal + team OKRs.
Quarterly OKR review surface.
https://app.lattice.com/goals - b/1-1
1:1 meeting agenda.
Managers and reports reach it weekly.
https://app.lattice.com/one-on-ones - b/feedback
Feedback / praise page.
Reach for cross-team feedback constantly.
https://app.lattice.com/feedback - b/engagement
Engagement / pulse surveys.
HR leadership reviews weekly.
https://app.lattice.com/engagement - b/lattice-admin
Admin section.
HR ops reaches it during cycle setup.
https://app.lattice.com/admin
Common workflows
Three patterns that pay back in week one.
01
Quarterly review cycle
Employees reach b/reviews + b/goals during every review window. Two slugs replace fragile email-link bookmarks.
02
Weekly 1:1
Both manager and report reach b/1-1 every Monday. The slug carries through every reorg.
03
Engagement survey review
HR leadership reaches b/engagement for monthly engagement reviews.
With and without
Same Lattice. Different team experience.
Without shortcuts
Each employee bookmarks Lattice from each browser separately. Review-cycle emails contain 200-character URLs.
With BookSlash
b/reviews, b/goals, b/1-1, b/feedback, b/engagement, b/lattice-admin. Six slugs cover Lattice for everyone.
Related integrations
Pair Lattice with one of these.
Frequently asked
BookSlash + Lattice
Same pattern, different destinations. Namespace if you have both: b/lattice-* vs b/cultureamp-*.
No — Lattice handles all submissions.
The integration fires inside Slack; BookSlash slugs work in browsers. They complement.
Yes — namespace cleanly: b/wd, b/rippling, b/lattice.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial