OSKAM UX + DESIGN PITA. I solve problems I value honesty humility diligence. I am Pita Oskam Nice to meet you

Transcription

1 PITA OSKAM UX + DESIGN me@pitaoskam.com While growing up, my godfather played a big part in my life. I started work at the fishery before I started school, vacuum packing fish while wearing a black rubbish bag as an apron. I would have looked adorable, I was little. When I got a little older he started giving me jobs at his magazine doing data entry, packing envelopes and licking so many thousands of stamps. I didn t have to lick them, there was a sponge, it was just back in the days when stamps tasted delicious. I solve problems I value honesty humility diligence I am Pita Oskam Nice to meet you The benefit of growing up in that environment; I was able to describe profit and loss before I learned my times tables. It also meant I grew up with strong business acumen. Once I had ditched the Huggies pull-ups and put on my big boy pants I moved into marketing, kicking things off in Account Management. I did so well that when I left the position, two clients hunted me down to offer me a role. I went with Nine Lanterns when they offered me Manager, Sales and Marketing. In my first year, through implementation of new CRM workflows, advertising and participation in industry events, my applied strategy increased company revenues by 40%. It is also where my journey into UX began as I up-skilled in aspects of technology, design and business analysis. My first UX role was for RedeeMe, a location based marketing platform. Being a startup my responsibilities were fairly comprehensive, spanning BA, Market Research, Branding, Visual Design, ID and wireframing. Several months after joining the project we approached VC. We were offered $1.2 Million first round investment. Five years later, having worked in start-ups and on large-scale enterprise systems, I m looking for a new challenge, working with great people who want to create something awe inspiring.

2 My approach to UX DESIGN I believe empathy is important, it allows you to see a problem from the users perspective, feel their pain, live their joy. It gives you the opportunity to leave yourself out of the equation and focus on people, helping them by listening and taking the time to understand. Due to my background in Marketing and Sales Management I have a strong understanding of marketing strategy. It plays a big part in how I approach UX in terms of brand management, user group segmentation, communications and personas. Possessing strong business acumen, I have a comprehensive understanding of business process and management, a key aspect in forming a UX framework that balances business requirements, strategy (mission, objectives, succession management, etc.) and user objectives. Having gained considerable exposure to business management in my life and career, it is a skill I have acquired. Whether looking at governance, project management (PRINCE2, AGILE, LEAN UX, KANBAN/SCRUM) or stakeholder management, this is the area that will make or break a project. Management is about forming and maintaining a shared vision. The diagram, below, shows an overview of my standardised approach based on Lean UX. Inception Preparation of project drivers and objectives for new initiatives or compiled from performance analysis Establish Requirements analysis, specification documentation and wireframes Execute Design and development to specifications Deploy Deploy to production environment and marketing launch Performance inception establish project management execute Analytics and functionality review according to KPI s from specification deploy performance

3 CEO INTRANET 12,000 USERS Prototype development, UX Research / Analysis / Design, UI Design, Front-end Development, Workflow Development, Ektron CMS. Research defined objectives: Implement responsive UI, restructure IA, restructure UI for content segregation (global/priority, navigation, content, communications and contextual sidebar), provide functionality aligned to planned department restructure and required communications for change management. Provide new functionality for information sharing and task allocation driven by intranet content. Process: A prototype was first created (Fig 1) to help form a business case within the organisation. Using feedback gained from the prototype, site analytics and user questionnaire I defined interaction workflows (Fig 2) to accurately describe functionality and user/system process before moving to design and development phases. Interaction workflows identified user touch points, interactions between different user types and system response/automation. Each element in the flow identified content users were engaged with as well as UI components required to proceed through their journey. Wireframes (Fig 3) were interactive and used by CEO stakeholders to test against initial requirements. Four content areas were used. Navigation remained in the same space as the old design, but the IA was altered slightly to avoid content overload (Fig 6). In the top bar there was considerable duplication of navigation items. These were removed and replaced with essential global items, search (Fig 8) and notifications (Fig 7). Content for consumption was placed in the centre (Fig 4) with contextual navigation for sharing and date pickers (Fig 5). and content requiring user action was placed in a right hand sidebar (Fig 9).

4 PLUTUS WEALTH MANAGEMENT SAAS PLATFORM Interaction workflow planning Widget type planning Report building tool functionality requirements Interaction workflow specification Interaction Design Permissions planning Wireframing (for specification doc and low fidelity guided user research) Visual design - user dashboard Global search 11 Responsive multi-level grouped tables Options button group 13

5 Currently being used as functional BETA by advisers and wealth managers to provide insights into account and portfolio information. Objectives: Create a client and adviser portal for productisation as SAAS, to reduce administration overhead, satisfy regulatory requirements and provide a unified view into multiple data sources. Process: Using rough wireframes (outlining reporting requirements) developed by the first client for the platform, interaction workflows and permission structures were defined. We then identified a set of widgets that could be used to meet reporting and content requirements. While not in Phase 1, a reporting tool was specified and considered within UI development, content management and communications approaches to ensure a consistent experience could be provided as functionality is added over time and customised user content is delivered. Due to demands on adviser s time and attention the portal s UI framework allows a user to switch between primary tasks such as communication, content engagement, search and information consumption, without losing positional context. IA/Navigation was kept flat with the majority of menu options being kept in the context of page content or widget content. For example, help is provided on a per widget/report basis (Fig 16) accessed through the options button group. With appropriate permissions, widgets can be added and customised in situ (Fig 17) when accessing dashboard edit functionality (Fig 20). Also, when the sidebar is open (Fig 18) the user can edit their own details (Fig 19). Tables are searchable (Fig 14) and feature multi-level grouping which can be expanded and collapsed (Fig 15) to ensure specific informtion can be found across pagenated content quickly.

6 OPENNEWS PLATFORM MVP PRODUCT UX Design, UI Design, Front-end Development, Workflow Development, Symfony. Objectives: Develop a new platform for the submission, management (rights and content), and dissemination of citizen journalism content. Process: A content workshop was held with the client to first understand the different target markets from a content submission perspective, and then from a monetisation perspective. Using information gathered, interaction workflows were created before drafting wireframes (Fig 1). Once drafted, wireframes were confirmed with the client and a clickable prototype prepared (Fig 2-4). The prototype was reviewed by a small user group and feedback collated. The platform was then developed as an MVP for use by the OpenNews Group internally. The front-end (Fig 5, 6, 8) was created for the project and took a mobile first approach. To meet the Admin requirements we used the AdminLTE theme (Fig 7 - OpenSource admin theme created by Almsaeed Studio). This has been used to provide usage reporting, user management, and moderation. Partnerships are currently in negotiation, which will confirm next stage development requirements. These include API development, and integration with 3rd party sites. Pita Oskam me@pitaoskam.com