The creation of this prototype is created soley on assumption of the process and delivery of a User Journey based on the realization that there is not an exact formula to do so.
Far too often when moving from project to project a portion of time is taken to learn another peers' workflow. This time may also include learning an unfamiliar software package and adjusting to working with completely new team members with their individual methods of production. The purpose behind User Journey Generator prototype was to eliminate the various methods and/or workflows that vary from peer to peer and adopt a single process for creation.
Finding a common workflow can create a more efficient process and a consistent bold statement of your brand that future and current clients will see while keeping uniqueness through projects and their content. The amount of time and effort saved using a unified process compounds over time yielding noticable results and less headaches.
As progression of the project continued, it opened up the opportunity to create a solution for consistent client-facing deliverables. This action not only helps with the production of user journeys but allows for single-user and multi-user interaction with individual control across multiple platforms.
Maintaining all data on a secure web server allows presenting to clients from any location in a single format which can be accessed at any time. This is achieved by a customized job code tied to NFC chip or QR code (platform dependent) — an alternative to using a login/password setup. When used in tandem with the client-facing application the client is presented their content based off of the job code and the user journey is generated. Handling requested content and processed internally prevents ever having to do any further development updates to the application itself, making it futureproof.
At first glance utilizing User Journey Generator as a system seems like a great solution for redefining and creating a consistent workflow and deliverable for both production and client. However, in the current development state there are certain cases or circumstances with this approach that can become unreliable and at times unusable.
The biggest issue is the lack of an offline mode, and the level of which the application relies on an 'always on' connection to the internet. With further development, an issue like this could be approached and solved with ease by creating content packs per case. The application can do an initial scan for additional content and offer the option to load from local source instead of an over-the-air method.
A second issue can relate to the project data size [disk memory] based off of content and optimization practices by the individual(s) producing the user journey. Though minor, the dependency of connection source and speed can elevate the time to retrieve all content for a project. A great way to help reduce data size would be the creation of a supplemental tool or suite of tools that would batch through completed content to return optimized yet high quality data.
What is great about the User Journey Generator and when it is most successful is the use of this system during client-facing presentations. Rather than printing out a large poster, often with text that is too small to read from a distance, each member would have their own personal screen allowing a more legible and personal experience. This also allows for the client(s) to walk through the interaction of their journey first-hand, which can help with further understanding of the task that is being presented.
On a much more broad spectrum the core functions in this prototype can serve additional uses not related to the initial problem at hand. Some of the underlying ideas can act as a gateway to solving unrealized problems in any industry for project management, client interaction, marketing, training, and many others unlisted.