by nirushiv on 6/16/21, 2:59 PM with 1 comments
by nirushiv on 6/16/21, 2:59 PM
1) find the right person or team to go to when things broke
2) onboard hires quickly, but instead bombarding them with a stream of links or huge docs that link to tens of other docs.
3) not knowing a valuable doc or dashboard existed or spending hours digging to no avail
4) providing endless support to external teams by sending links on an ad-hoc basis through Slack/Teams. When we tried public-facing docs for our teams, they inevitably went stale because 'out of sight, out of mind'.
We're tackling these four issues by
1) Backlinking - got paged and found yourself on a team's dashbard page? Our browser extension links you back to their Pinbase page (if the've pinned the dash) so you can see who's on the team and leverage the other documentation they've deemed public.
2 and 3) making Pins flat (non-nested) and easily searchable and tagged with, for example, #ramp-up or #oncall. We've found that flatness reduces cognitive load by an order of magnitude, because it gives a source-of-truth that does less deferring to other sources. If you have 10 design docs, pin each of them rather than a Dropbox folder called 'docs', and we make the search good enough to find.
+ making pinning easy (1-click) through our browser extension, so you don't have to break your workflow to pin something that may help a teammate (or yourself) in the future.
4) putting Public and Private Pins on the same page, color-coded, so your team looks at each on a daily basis. If a private Pin (maybe a dashboard for your new service) should be public, they can just drag and drop it to change visibility. Only need your team to know about your #staging stack? Put it under 'Private', because other teams are unlikely to need it.
There are 8 teams currently trying out our product and giving great feedback. If you'd also like to try it out, there is a form on the website to get access (in the next few weeks, based on backlog).