Hacker News new | ask | show | jobs
by w10-1 821 days ago
Other prior art includes IDE monitoring.

Other tie-in's include task switching and context saving. Remember Eclipse Mylyn would save the state of the IDE associated with a task, and even associate that with a bug so another developer could pick up the world of the task.

Indeed, rather than integrating with other applications by snooping them (raising confidentiality and security issues), you might consider making a legal workspace that can publish out, producing word docs or pushing url's to browse, etc. That way, people accept that everything in context is monitored, and you can automate the crap out of any use case.

The Attorney-IDE is also how you can secure the environment, encrypting everything and even ensuring that information doesn't flow from one client to another. That could become a sales point for them to mention to their clients: that all client information is separately secured, with keys revocable at a moment's notice.

The key feature for usability of this information is seamless provenance for secure internal collaboration: all information should come with information about where it's been, who's seen it, etc. (Just don't say blockchain). If you want to add features for the managing partners to feel like gods, give them the ability to search all contexts without decrypting, so they can implement some policies while maintaining confidentiality for clients.

Business-wise, you can start with a few firms via high-touch custom integration with their policies and practices, and gradually productize through generalization and customization/assembly as you move to low-touch sales model. I suspect each use-case gets system/AI customization you can deploy out, so with luck you'll always have leading-edge high-touch feature development followed by broader deployment.

If you want the (monitored) attorneys themselves as stakeholders, layer in features for continuous tracking, to identify time-wasters (admin like time-tracking, new technology evaluation like research via Lexus vs. some new internal AI) and even negotiate or enforce ground rules (associates limited to 60 hours in exchange for lower salaries...)

1 comments

This is very interesting. We have thought about a few of these ideas and will continue to mull over the others. At a high level, I could imagine provenance being less important but time savings through automation to be highly important.

Love all the detail here.