‹ Home
Exported

TOLOGIX - ISLG App Rebuild

Laura Mindorff, COO at IndustrialHarsh Parikh, Tech Lead at DevITMelissa Cowell, General Manager at IndustrialHiren PatelMonica Martinez, MonolabMarysia RaptisPaul MoonIrit WeinfeldPatrick Harris, Web Designer at IndustrialPiyush Kanpariya, DevITRob Wiesenberg, ContegraRadomir Mladenovic, ContegraKetan Sondarva, Technical Project Manager at DevITStephanie Ducasse, Web Developer at IndustrialAkash Buch +16 others
Added by Stefanie Gibson • Updated

'Trend Analyzer' - June 8

Hi Morgan,
For your reference here's the design we went over today with a general structure for this tool. As mentioned, I'm putting together a document so we can map out all of the canned reports, search filters and fields for creating custom reports so we'll send that along on Monday.
Thanks,
Stef
Case Analysis Tool (1).pdf 42.8 KB • Download

Comments & Events

Morgan Maguire, CEO Morgan Maguire, CEO
Great. Thanks for this Stefanie Gibson, UX Researcher at Industrial Stefanie . I'll take a closer look at this when I have a chance next week.

Have a good weekend.

Morgan 
Notified 3 people
Stefanie Gibson, UX Researcher at Industrial Stefanie Gibson, UX Researcher
Hi Morgan Maguire, CEO Morgan ,
We've prepared this simple document to fill in. I think if we start with the pre-canned reports and user goals/questions associated with each, we can more easily determine how users will navigate to their custom reports and what some of the default tables (like the arbitrator one in the wires) should include and be filterable by. I can probably infer everything else from this and get feedback on it. 

To fill this out, we want to start with what question to user has (so we can understand the motivation), then we can get into what the report is and the exact default report data included. I put in some examples, knowing that these might not be the ones you were thinking of. As I mentioned Friday, I think we can allow users to edit the columns and add more data to the report and save it. 

Let me know if you have any questions. 

Stef
Notified 3 people
Morgan Maguire, CEO Morgan Maguire, CEO
Hi Stefanie Gibson, UX Researcher at Industrial Stefanie ,

Just wanted to let you know I'll be pretty the rest of the week, so I probably won't get to this until next week.

Thanks,

Morgan 
Notified 3 people
Stefanie Gibson, UX Researcher at Industrial Stefanie Gibson, UX Researcher
no problem - I've been working on other changes to ISLG this week. 
Notified 3 people
Morgan Maguire, CEO Morgan Maguire, CEO
Hi Stefanie Gibson, UX Researcher at Industrial Stefanie ,

I just wanted to shoot you a note to let you know I haven't forgotten about this. I plan on taking a closer look when I have an opportunity to think about this in more depth.  Hopefully I'll have some time tomorrow, assuming my day doesn't get hijacked with other issues.

Thanks,

Morgan
Notified 3 people
Morgan Maguire, CEO Morgan Maguire, CEO
Hi Stefanie Gibson, UX Researcher at Industrial Stefanie ,

I have taken a more in-depth look at the canned reports document, and tried to create a series of reports that would be most useful to users. Hopefully this gives you a better idea of the data relationships within the Case Analysis Data Structure spreadsheet (see updated version here). Here are some general comments about what I've added:
  • All report categories have reports on the findings of tribunal/annulment committees. I omitted reports that connect the different categories to the Navigator and Citators, because I wasn't sure if this should be presented differently through other tools.
  • I have consolidated Arbitrators, Counsel, Quantum Experts and Tribunal Secretaries into one page of reports on People, because it is common for people to have "worn multiple hats" (e.g., acted as both arbitrators and counsel), and we want all relevant information concerning a person to appear on the same page. My suggestion is to have each person's report be customized according to the different roles they've had.
  • I removed the reports that focus on sector and subject of dispute. This data may be useful for customized reports, but it shouldn't be a focus for the canned reports.
  • I have omitted important metadata, including dates when cases began/concluded; however, I quickly realized that the number of meta fields quickly becomes unruly. Therefore, I suggest we come up with methods that allow users to quickly add/delete meta fields, and perhaps have a lateral scrolling option when the number of meta fields gets beyond what will fit on the screen.
Let me know if you have any questions or concerns. Otherwise, we can discuss more during our call next Thursday. 

Thanks,

Morgan
Notified 3 people
Stefanie Gibson, UX Researcher at Industrial Stefanie Gibson, UX Researcher
That's great thanks Morgan. I'll go over this later today and let you know if I have questions. 
Notified 3 people
Stefanie Gibson, UX Researcher at Industrial Stefanie Gibson, UX Researcher
This is great Morgan, thanks. I don't have any questions for now - this gives us enough to run with. 
Notified 3 people
Morgan Maguire, CEO Morgan Maguire, CEO
Great. Glad to hear it. We'll discuss more next week.

Have a good weekend!

Morgan
Notified 3 people