Welcome to your NEW process
Capture critical context for important decisions.
Collaborative search and bookmarking.
STEP 1
Team member creates a research notebook.
STEP 2
Each team member receives an email with a link to the notebook.
Use the bookmarklet to add links to the notebook.
No browser extension needed. Add our bookmark to your toolbar, nothing more.
STEP 3
As you browse, add bookmarks to the notebook.
Add images, videos, tables to the notes.
FINISH
Auto-summarize your findings at any point utilizing GPT-3.
STEP 4
Application level encryption utilizing 256-bit AES-GCM.
Your best engineer will quit one day
Capturing how they arrived at a decision
is just as important as the decision itself.
A wiki summary, a long-ago email, an old Slack conversation, is simply not enough.
A shared space for semi-related ideas
There's a weird space where big decisions have to be made. Between all of the planning meetings, hundreds of open tabs, Slack conversations and conclusions, lies the context.
Between planning and decision, everyone on the team has their own research, their own notes, living somewhere on their laptop. It matters when the bookmarks were added. Vendor offerings change. Architectural decisions change as the scale of the engineering team grows. New features are added since you last made a decision.
The timeline of information matters.
You need a centralized place to dump these bookmarks, these ideas. You need a frictionless way to record bookmarks, images, relevant data points, searches.
Searches, bookmarks, timelines
- key pieces of context.
When your software development team is making a key decision, what do you do?
Probably send out an email to the C team announcing the upcoming change or feature.
Maybe you update a wiki page outlining your vendor comparisons?
Or how about when a key engineer leaves your team, how do you know that all of the company knowledge has been recorded, in detail? Key decisions are more than just a summary. When you’re researching something for your team, you have 10, 20, 30 tabs open. Tons of Google searches. You’re doing data comparisons. Bookmarks. Notes. Then finally, a summary.
But once you’ve reached your summary, don’t throw away the context.
Those tabs, those searches, those notes of why or why not you went with a certain vendor/architecture/solution, are all important. Your team’s search history, their bookmarks, are key to understanding why you made a critical decision. Your engineers should be bookmarking which sites they visited. They should take notes as they research, recording their nuanced thoughts.
Critical context gives each of your team-members a simple bookmarklet for each document. Whenever you visit a site that’s relevant to your key decision, click the bookmarklet, capture that context. You get to see each team member, their searches, their bookmarks, their findings, in chronological order.
When you’ve finally reached compiled enough items, Critical Context can auto-summarize your points and email your teammates with the findings.
When you're researching big ideas
capture that context
at the moment of inspiration.
Insightful ideas fade fast.
Use Critical's inline search to record your ideas at the speed of thought.
Capturing the thought at the time it occurs is more important than organizing the thought. Great ideas happen all the time. At a moments notice. Then just like that, the idea is gone. You need a quick way, a quick mechanism for capturing that information. The context. The nuance that makes it workable, doable, brilliant.
Just start typing. Search results are updated in real-time. Never leave your tab for critical information.
Can your development team
capture more of their findings,
capture more of their research,
create better documentation,
without more effort?
YES.
Without being burdened with additional process?
YES..
Share their findings with the team and even publicly?
YES...
Without sacrificing their privacy?
YES, YES, YES!
But we already use
Confluence/Google Docs/Microsoft Teams.
Critical Context is complimentary to these great products. Critical Context allows you to capture what led to your key decision, not the key decision itself. And when you’re done capturing notes and bookmarks, you’re free to export your findings to your favorite document product.
You mentioned my search history
- are you tracking my browsing?
No, not at all. For each Critical document, you’re provided a bookmarklet. You just pull the bookmarklet up into your browser’s toolbar. Then, every time you visit a site that has something meaningful to your research, you just click the bookmarklet, record the URL and your notes, and that’s it.
Do I need to allocate engineering resources to get up and running?
No, not at all.
- Invite your team members.
- Create a notebook.
- Everyone adds their research via the bookmarklet.
"We don't need another tool."
We hear you.
Between Email, Github, Slack, Confluence, Google Docs - so many places where “things” could be.
- We plan to roll out a Google Docs and Confluence export feature in the next couple of months. You’ll be able to export all of your notes and summaries, automatically, so that they are where you prefer to search for them.
- So now you’re probably asking yourself, why would you sign up today when I can’t export. Because if you sign up today, we’ll give you 20% off your subscription.
We’ll also give you a 30-day money back guarantee. If you don’t think Critical Context enhances your teams ability to do research, if you think it's just “yet another note taking app”, then cancel within the 30 days, no questions asked.