Our user research started with four key areas of Lloyd Register's marine plan. In each survey plan conducted by specialized personnel who are expert in various asset management and reporting. Once I identified the personas I had conducted interviews and field visit to the actual user location and collected various data point that are important to understand user need.
An Asset System (AS) contain all data pertinent to an asset (a vessel or management system).
Job Management (JM) defines, which survey requests and other internal/external requests (e.g. class certification suspension, transfer of class out, asset reactivation etc.) will be recorded, surveys scheduled and relevant details drawn from “Asset System” (AS) will be provisioned to the Surveyors.
Survey Reporting Tool (SRT) – to be used by Surveyors to load the required details of the Job (Service Requests) and Asset and undertake requested actions. They would then issue certificates and generate survey reports using SRT.
Survey Reporting Process (SRP) – to update Service Schedule of the Asset by applying scheduling rules after the Survey report is authorized.
My approach was to start with quick whiteboarding and hand sketching. Then iterate through focus group analysis and at times validate using quick paper mockups. At I already identified the key user tasks so the mock-ups were more aligned to cover those scenarios as per the earlier research-finding.
Identify scenarios that trigger an LR process, define scope and prioritise by volume, value, visibility
Develop a solution-free view of the “To Be” business processes
Identify and highlight steps within the processes that invoke Functional Requirements
Identify new requirements that are apparent from the business process
Rapid prototyping can mean the difference between quickly finding a path to a successful product and toiling away at a pipe-dream for months. Putting together a prototype will force every stakeholder of the project to think through the details and user experience of my product ideas. Once I have a prototype, it helped me to collect detailed feedback and iterate.
There are a couple of assumptions I had made during my prototype:
a) It's only going to be viewed in modern browsers, including during user testing and if the link is sent to a client.
b) The HTML code was never made for actual development.
A UI specification defines the rules of engagement for a user interacting with a specific page or screen within an application.
My UI specification for Plotstar contains:
a) Visual overview of the screen.
b)Breaking the screen up into sections and individual visual elements.
c) Assets such as icons, images etc for various phone resolution.
d) Delivered Interaction details and visual comps.
e) Final sign off the project.