Like many of my colleagues at Shockoe, I began writing computer code in a high school classroom. However, in my case, the school was particularly advanced for its time in offering such a course, and our “computer” was a keyboard, dot-matrix printer, and a modem connection to the University of Virginia, where the actual computer occupied an entire floor of a large building. And while most of those colleagues went on a path that brought them relatively quickly to Shockoe, I spent two decades working as an attorney in New York, Seoul, and Virginia.
Now in my third year of software development I have felt particularly happy to be at Shockoe because I believe it addresses needs that I often saw during my time working as an attorney, needs that I am certain are shared by many industries.
In my experience, the following was typical of the manner in which law firms implement technology. First, the decisions are made by senior partners who, being busy with the representation of clients, have little time to keep up-to-date with what is available or most desirable in technology. This leads either to an “if it ain’t broke, don’t fix it” mentality, or an attempt to take care of the problem in one fell swoop with a package solution that may or may not fit comfortably with the way they have set up their practice. In the latter case, the acquired technology may go unused, or used only to the extent required by the firm. For example, if a time-tracking application is difficult to use, an attorney may keep track of his time on post-it notes as she always did before, then have her secretary type it all into the application at the end of the week.
In either case, what then happens is that employees begin finding their own solutions. Each attorney and his or her assistants devise their own system, piecing together hardware and applications as they see fit. Depending on their level of technological sophistication, they may, or may not, arrive at a solution that works well for them. However, this approach drastically reduces the potential for collaboration, and creates a host of potential problems, as the less technologically-adept might adopt solutions that introduce security vulnerabilities or other problems.
Although so often noted as to sound trite, an average employee today with a typical mobile device is comparable to an employee with superpowers two or three decades ago. To make the most of those powers, however, requires sophisticated solutions. This includes, of course, a focus on the possible pitfalls of any new technology. A device that allows employees to watch training videos at convenient times may also allow them to spend the working day watching Netflix. Large collections of data become valuable, and thus must be protected, not only from hackers in foreign locales, but from disgruntled or former employees. Yet while minimizing risk demands much attention, it is just as important to make certain that new technology is used to its full potential. Making one’s workforce five times more efficient is simply not good enough in a competitive business environment if the competition makes their workforce eight times more efficient.
This is what excites me about working at Shockoe, being able to use my skills to allow our clients to make the greatest possible use of the technology available to them. Apps created now increase employee productivity, streamline task performance and ensure employees have real-time data access they need for day to day exchange opposed to the opposite stagnant mentality. If this sounds familiar to you, check out our work for Financial Services Mobile Technology and contact us for any innovative ideas to help your team tackle your digital transformation with a great mobile strategy.
Dear New Client
We are so glad you have trusted Shockoe to help accomplish your business goals. We understand that for this particular project, you need to design and build a new workplace productivity mobile app for your employees. Here are some highlights of what you can expect throughout the course of this project.
Project Set up and Kickoff: The kickoff meeting will provide an opportunity for all team members to meet, review the project scope, timeline and processes, and discuss any anticipated challenges. Topics covered will include milestones and key dates, responsibilities, recurring meetings, status reporting, how we will work together, and contact information.
Discovery: Once we’re out of the gate, we will interview your stakeholders and subject matter experts to deepen our understanding of your business model and goals for this project. A Shockoe user experience strategist will lead this effort and may suggest activities such as market research, competitor analysis, identification of user personas, or a heuristic evaluation of your current application. Along the way, we will document your requirements and create user flows and user stories. Typically, a user interface designer is involved in this phase as well so the transition to design is seamless.
Design: Once we have outlined what your new application needs to do, our design team gets to work. These folks are the masterminds of creating a top-notch experience for your target audience. They start by creating mockups (wireframes) that show the key elements on each screen and how a user progresses from screen to screen. These mockups are easily transformable into clickable prototypes if desired for review by your team or to conduct usability testing with a sample audience. Beyond that, we bring your screens to life with a style guide and high-fidelity designs. Together these paint the picture of how the application will look and feel and will include actual colors, fonts, and images.
An agile-like process: Typically, at some point between the transition from Discovery to Design, we will start to employ an agile approach to the project. The goal is to share our work early and often so that you have visibility along the way. Together we can determine the right amount of upfront user experience planning that’s needed before we move into iterative sprints. Sprints are typically two week intervals where we identify an area of the app on which to focus, we wireframe it, apply the design, and build it. The sprint culminates with a demo at the end where we share our work and gather your feedback. Everyone looks forward to demo time!
Development: The scope of the project determines how many sprints are needed. No matter how many two-week intervals are involved, the process is the same and all members of the team know what to expect. Each sprint includes sprint planning, development of the relevant user stories, a day or two of testing and issue resolution, and finally, the sprint demo at the end.
Testing and launch: After the last development sprint ends, we spend a couple of weeks regression testing, which is thorough testing of the entire app to ensure that all functionality is working as expected and that there are no display issues across supported devices. Any issues identified are resolved and then the app is turned over to you to perform user acceptance testing. Fortunately, you will have had access to the app at each sprint demo when the QA version of the app is uploaded to Shockoe’s server for download. This testing at the end of the project is an opportunity to execute all test cases and confirm the final product is ready. Beyond that it’s just a matter of planning for submission to the app stores. Shockoe can either help you through that process or submit the app on your behalf.
We are with you throughout the life of the project and let you know what to expect at each step of the way. We find that by the end of a project, our collective team has bonded in a way unlike no other. We are working together to produce something that will make people’s lives better in some way. And that’s a great feeling. Thank you for letting us be a part of it.
Let’s get started . . .
The Shockoe Team
Shockoe’s Mobile Training Team has been helping Enterprise Organizations for the last 3 years with Mobile Development Training and is now offering a brand new class focussed on helping organizations create mobile strategies. Too often we work with clients that deploy mobile solution without a vision, not focussing on the end product and then work countless hours to ensure its success.
If you are embarking on a new Mobile Project, this session is for you. join us for this 3 part series as we teach you how to set a vision for your mobile projects.
[av_iconlist_item title=’The Mobile Ecosystem’ link=” linktarget=” icon=’ue8a3′ font=’entypo-fontello’]
Join Us On: April 7th, 14th, or the 21st
[av_iconlist_item title=’The Mobile State and TCO’ link=” linktarget=” icon=’ue841′ font=’entypo-fontello’]
Join Us On: April 9th, 16th, or the 23rd
[av_iconlist_item title=’The Business Case & Mobile Roadmap’ link=” linktarget=” icon=’ue849′ font=’entypo-fontello’]
Join Us On: April 11th, 18th, or the 25th
[av_contact email=’firstname.lastname@example.org’ button=’Submit’ title=’Contact Us’ sent=’Your message has been sent!’ subject=’Mobile Strategy – SignUp form’ autorespond=” captcha=”]
[av_contact_field label=’Name’ type=’text’ options=” check=’is_empty’ width=”]
[av_contact_field label=’E-Mail’ type=’text’ options=” check=’is_email’ width=”]
[av_contact_field label=’Phone number’ type=’text’ options=” check=’is_empty’ width=”]
[av_contact_field label=’Company’ type=’text’ options=” check=’is_empty’ width=”]
[av_contact_field label=’Coments’ type=’text’ options=” check=’is_empty’ width=”]
*Photo source onbile
Aiming to leverage its best-in-class web platform, the University of Richmond set out to build a cross-platform app that achieved three main objectives:
- Allowed users an unparalleled ability to customize content and receive notifications specifically tailored to their individual interests;
- Established a comprehensive application platform for all future mobile projects;
- Integrated with the skill sets and workflow processes of the web development team.
Take a look at the UR app in the Apple App Store .