Krush

Mobile Application
May 2018- July 2018
The habit loop being explained







Krush is an application for data collection, analysis and access for people involved in the process of Stone Crushing.






Project Brief


Stone crushing sites are located in far off places. Frequesnt visits can't be a method of keeping up with the happenings. The client wanted to be able to access information regarding these sites easily and keep track of the current situation. Data collection and analysis is a big part of the exercise which is done with the help of WhatsApp and Microsoft Excel. The client wanted to convert this process into an application.

Research




The process began with me trying to understand the current situation and the kind of work that happens at these sites.

The quarry is blasted, the stone is then crushed to preferred sizes. This crushed stone is shipped to various construction sites.

  • Removal of the top layer of soil
  • Drilling and adding blasting material
  • Blasting
  • Carrying the stones from the quarry to the crusher
  • Crushing and segregation into stones of different sizes
  • Delivery of the stones to the construction sites
Gif explaining the process

OFFICE

Needs
  • Easy access to data
  • Analysis of the available data
  • Availability of the data & analysis at all times
Challenges
  • Lack of awareness of technological advances
  • Results of analysis need to confirm
Opportunities
  • Availability of a computer
‘I want to be able to know the exact status of the happenings at all times’
Challan

SITE

Needs
  • Effortless and intuitive methods of data collection
  • Introduction of a workflow
Challenges
  • Mobile phone is the only device available
  • Although not inexperienced, understanding of technology is limited to applications like WhatsApp, Youtube etc.
  • Shift from a paper based system to a digital system
Opportunities
  • The supervisor is literate and understands English.
‘I want the effort in the transfer of data to reduce’
Challan









Persona

Picture of the Owner Persona

Mr. Subhash, 42 CEO

Subhash loves all things technology. He is constantly looking for ways to streamline his business and reduce waste. He has a lot of things that need his attention and wants to use technology in his favour to receive and analyse data.

Behaviour
  • Tech savvy
  • Looking for ways to innovate
  • Is good at thinking of the big picture
Motivators
  • Increasing business revenues and profits
  • Create more efficient processes
  • Identify and resolve pain points
  • Recognise fraudulent behaviour
Needs
  • Make better decisions based on data
  • Quick, fast results
  • Availability of information at fingertips
  • Easing the process of issue resolution
  • Wants control of the whole system
Challenges
  • Field Execution
  • Financial resources
  • Proof of concept
  • Recognising fraudulent behaviour
  • Data needs to be reliable



Picture of the SUpervisor Persona

Mr. Raosaheb, 32 Supervisor

Raosaheb is active on the internet and engages with friends. He is the person of contact for any crushing site. He is aware of all the happenings at the crushing site and is expected to report to the CEO's assistant in case of mishaps.

Behaviour
  • He has been trained at ITI
  • Is aware of how to use WhatsApp, Youtube, TikTok etc.
  • Can read and write
Motivators
  • Wants leisure time for himself
  • Would like to stay inside the shed as much as possible due to the dust and noise at a crushing site.
Needs
  • Wants feedback on the work and data that has been collected
  • Visits to the crusher should be reduced (due to heat, dust and noise)
Challenges
  • The accuracy of data collected
  • Recognition of fraudulant behaviour






Findings
Image showing the data







Problem Statement


1.0
How might we make the process of data collection and analysis easier.


2.0
How might we make the process of data collection, analysis and access easier for all the people involved in the process of stone crushing.









Information Architecture*


The Information Architecture represents the kind of information that needs to be collected,the correlation and usage and not the app architecture.


Information Architecture


2.0 Information Architecture









Paper Prototypes


Paper Prototypes were used for user testing with the supervisors to gain a deeper understanding about the Information Architecture'


Paper Prototype 1

Paper Prototype 2

Paper Prototype 3

Paper Prototype 4

Paper Prototype 5

Paper Prototype 6











Prototype 1.0


User Testing led to

  • Changes to the Information
  • Change in arrangement to improve accessibility and usage
  • Increase in the number of fields and accommodation at the right places
  • Change in priority of fields for easier access

Wireframe 1

Wireframe

Wireframe










Prototype 2.0


User Testing led to

  • Change in Information arrangement to improve access
  • Realisation for the need of two user groups: Owner & Supervisor
  • Removal of excess elements
  • Customisation of information input according to the site’s need

Prototype

Prototype

Prototype










Prototype 3.0


User Testing led to

  • Change in hierarchy of data
  • Reduction of cluster
  • A lot of inputs from Google Material Design

Prototype

Prototype

Prototype










Prototype