Warren's Process Journal @ USC @warren-usc-blog - Tumblr Blog

Process Journal: Reflection

The creative problem solving process contains seven steps — accept, analyze, define, ideate, select, implement, and evaluate.

Accept In the accept phase, we try to understand the problem, create motivation for it, and become responsible for devising a solution. There are many times when I’ve rejected a problem, only to find salvation in others who were more ambitious than myself. Just speaking with them innately sparked creative passion to a solution. The acceptance phase doesn’t have to be a solitary task, but rather it can be a group therapy session, where you vent your feelings to your team.

Analyze In the analyze phase, we explore the challenge in a number of ways — journaling, idea dumping, data collecting, competitive analysis, pattern recognition, and more. I find that the analyze phase can be enhanced by carrying out tasks with a teammate. This will help you guys discuss the problem together and add a different perspective on the artifacts collected. By working closely in this phase, your teammate will bring insight to you that you wouldn’t have otherwise.

Define In the definition phase, you are identifying key issues, redefining the problem, naming key tasks, and developing a persona. Lastly, the audience and measurable objectives are established after the fact. This can be improve significantly if we reversed the steps, looking into the audience and measurable objectives first. By establishing project constraints to help meet project goals, you facilitate the definition process by helping to eliminate ideas that do not meet objectives. The audience is also important to think about when defining the problem. They are your target demographic and if the problem definition doesn’t meet audience expectations, then you may have to redefine the it.

Ideate The ideation phase involves brainstorming either by yourself or with a group. I find that there are excellent group brainstorming techniques that will help shift your perspective, leading to fresh ideas. For example, an empathy map forces you to think about the user — what they’re feeling, thinking, seeing, and doing. As a group, we can user stickies to list out user goals or scenarios and continue until we’ve listed out everything. Then, we can list out specific features that would satisfy that specific goal.

Select In the selection phase, you choose a solution from the ideation phase as you validate each option against the initial objectives. To improve the process, you can use a variety of techniques. A red route analysis can determine the importance of product features and the percentage of your users each feature will impact. You can identify constraints based on resources (financial and human) to help understand the practicality of the solution. We can see what competitors are doing and evaluate the market. These techniques will help us select the best possible solution.

Implement In the implementation phase, the real work begins as the team formulates the steps to create the product. The actual product development occurs, communication is critical to the project success. A software management tool like Pivotal Tracker or Jira would improve the team dynamics immensely. It’ll help the team manage the tasks and the project manager to understand the current progress. Slack, an online collaboration tool, has been excellent resource in helping my team at work stay connected.

Evaluate In the evaluation phase, you receive feedback on the design solution from peers, user journal to self-evaluate performance, reflect on mistakes, and self-manage the next steps. Evaluation can be vastly improved with anonymous feedback, where people can talk freely without penalty.

Process Journal: Conceptualize It

Full Presentation: https://docs.google.com/presentation/d/10EV5ObNyL6fnnGnTsP7MTYZKA1dRNrZRwkpEohOkSdo/edit?usp=sharing

Process Journal: Evaluation

There are multiple techniques used to evaluate the performance of the group. Peer feedback from other class members and the professor has been a huge asset in helping to steer the project direction. The journals have also been a great way for us to reflect on our progress and understand our current shortcomings and strengths. They help to document the progress at each phase of the creative process. To assess the outcome at each phase, we take a combination of the feedback and our own reflection in the journal and validate it against our established initial goals.

For the solution itself, we established a criteria in the problem definition phase that we should follow at subsequent phases. Some of which include: - Ensure solution is technological feasible - Concept should be a minimum viable product - Solution is well received by the target demographic - Solution should be seamlessly integrated in to the user’s work environment - Solution should effectively achieve user goal of modulating awareness

The criteria became the guiding principles to validate our solution. In the ideation phase, it helped us identify the specific product features that would suit our needs. In the selection phase, it helped us narrow down those ideas into a solution that would meet our business goals. In the implementation phase, we used the criteria to expand on our ideas and create the business model canvas. Establishing a set criteria has facilitated our creative process and helped us self-check our solution at each phase.

Business Model Canvas

Process Journal: Implementation

Team Onspyre is planning on multiple visuals to help communicate our method of implementation. The first is a diagram that will reveal our process for research, prototyping and testing. The process for design is rarely linear, and the team may switch back and forth between phases. By establishing an official process, the team can avoid confusion and better understand the current phase. To pitch the idea to stakeholders, the team feels they need to provide context for how it will benefit workers in high risk environments. A storyboard that will show key scenarios can help portray the dire safety need and how the innovative solution will help reduce human error. The storyboard is borrowed from the film industry and will provide a narrative of the persona, construction worker, and the solution as it would apply to their work environment. The team will attempt to create a model of the product and wire-frames for the companion app.

Choosing a Solution (Group)

How might we modulate body and mind to avoid accidents?

Solution: Protective Eyewear 

The product must meet safety requirements for impact as well as heat and chemical resistance. 

Features

Monitoring tech:  

A combination (EEG, sEMG) 

Body temperature 

Heart rate 

Additional tech: 

Companion mobile app (iOS, Android) 

AR for messages/images to be displayed 

Audio 

N2H: Machine learning (could be deployed in v2) 

Modulation: 

Alerts/prompts to self-check 

Pulsing or vibration 

Audio guidance - music, guided breathing 

N2H: Bio-modulations (i.e. light, vagus nerve) 

Guidance, Proactivity: 

Preferences - allows user to customize level and type of modulation 

Device prompts you to self-report state of mind and emotions to help validate information inferred from data. 

Data:  

Dashboard that displays user’s historical data. User can choose level of engagement. 

Personal data available only to the user 

Anonymous data available in the aggregate to company 

Process

Criteria used:

Established goals (elements and outcomes our product must have) and weighed ideas to accomplish/exhibit these

For a first phase release, determined features that would fit into a minimum viable product, saving additional features for future releases 

Determine minimum tech that monitors physiological data and add-ons that would be beneficial 

Consider user concerns such as privacy and level of modulation 

Pragmatic & Logistical concerns?

Complex ideas like machine learning, bio-modulations 

Integrating the different sensors and bio-modulation options.  

Regulations: bio-modulations, certification of safety glasses, potential OSHA input 

Workers may feel they would be under more scrutiny and pressured to provide data in court of law  

Compromises:

The initial release will begin with an MVP (version 1) product for these purposes.

Technique:

Kepner-Tregoe Method: used individually

Reflection:

The team came together and collected all the initial features from the ideation phase. We spent some time individually to bucket the features and rank them on a scale of 1-10 (Kepner-Tregoe Method). Afterwards, we gathered features we all agreed upon based on our rankings into a final solution document. For features that we disagreed upon, we debated them across multiple dimensions:

Minimum viable product feature

Abides to user goals

Feasible technology

Maintains user privacy

Product would have positive reception by users

After our discussion, we found that an inevitable problem with the solution is the concern with scrutiny of workers who adopt the product. This would especially be a concern if the workers commit to an error while performing a high risk task that results in damages. The court of law may pressure the user to release their data, which we seek to protect.

Process Journal: Selection

Our group listed all the features from our ideation phase. When selecting the features initially, we listed higher level goals that helped form a set of criteria. We wanted the first phase of the product to be simple and iterative, a minimum viable product. This way we can learn from customer usage and make informed incremental improvements, similar to agile software. Basically, there would be a core product that helped to monitor the user’s awareness and help modulate them when performing high risk tasks. Additional add-ons can help improve modulation, such as a breath analyzer to determine the chemical contents in the user’s breath. We explored a lot of eccentric ideas, which got eliminated in the next step.

We then bucketed the features by must-have and nice-to-have, a software engineering technique where nice-to-have features are placed in the backlog for future iteration. Individually, we ranked the features on a scale of 1-10, following the Kepner-Tregoe Method.

Individual Ranking:

Finally, we came together as a team and saw where our feature ranks converged. We began the final documentation and debated discrepancies together. For the most part, our team was in alignment on the main core features. We were ambivalent when discussing machine learning. Was this something that we can omit in the first pass and still launch a successful product?

An underlying concern for our prospective users, which is an inevitable part the product’s nature, is that workers may feel they are under more scrutiny. Even though privacy is a huge priority for our team, if there are damages as a result of a human error, the court of law may pressure the worker to release their alertness data. This may cause fear of adopting the tool into high risk work environments.

Ideation

Process

Our group borrowed ideas from the fishbone diagram to list out the underlying causes and reason for accidents in high-risk work environments.

We spent the next 10 minutes posting stickies for user goals, framed “As a user I want...” This helped us build empathy and think about the product direction from the user’s perspective.

We came together and discussed each user goal and grouped them by similarity. This is a fundamental concept in affinity diagrams, which can be used to organize thoughts and see recurring themes.

We spent an additional 10 minutes listing out potential product features that can meet the intended user goals. The features (yellow) were listed right next to the user goals (blue)

Key Takeaways

Users would like to avoid distraction when they perform high risk tasks that are prone to accidents. The new technology piece can become a distraction, and a hindrance if it’s not carefully designed. Basically, the tech should be invisible to the user’s workflow and provide stimulus only when it’s essentially helpful. Users may also feel like certain modulations are invasive. To mitigate the risk of distraction and invasive feelings, the product should allow the user to customize the impact of the device through user preferences.

Aside from EEG signals, data points from other sensors can prove to invaluable in informing the system of user fatigue, alertness, frustration, stress levels, etc. Examples include changes in blood pressure, cortisol levels, body temperatures, galvanic skin response, oxygen and carbon in breath, and their heart rate. To confirm the user’s current mental and physical state, the system can probe the user with a question. Ex — “On a scale of 1-5, how stressed are you...“ Questions that help the system validate the information deciphered from data would be immensely useful to improve the intelligence of the system.

Users may be conscientious of their privacy and how that data might be accessible by their employer of an organization. As a result, statistical information on employee performance from the product should be anonymous and used strictly for analytics purposes. The data should be used to understand the overall group performance, rather than to scrutinize an individual.

Group Brainstorming and Debriefing Session

Team Onspyre used Google Drawing as a means to collaborate. We listed out the user goals we wanted, followed by specific product features that can meet those goals.

Root causes (pink) and reasons for accidents (green) are shown in upper left.

User goals are shown in blue.

Stickies were grouped based on similarity, an affinity-diagram methodology.

Product requirements (yellow) are listed near associated user goals.

Definition

My individual problem definition can be found here: View Individual Problem Definition

To develop a priority of features, I took to the morphological analysis from the previous week. I looked at features that can help create a minimum viable product to prioritize those features that are necessary for essential functions. Other features can be thrown into the backlog.

1. Biological sensors 2. Bluetooth connectivity 3. EEG sensor 4. Accelerometer 5. Software 6. Audio guide 7. AI / machine learning 8. Cloud computing 9. Analytics - visualize information from sensors 10. AR/VR 11. Environment / spatial awareness

I used sketches to attempt to help flush out some initial ideas. It helped with translating my feelings into visual form and words.

I looked into reference materials that provided information on fatigue and performance. View my initial research findings

I used mind mapping and the research I found to try and uncover the root cause when someone loses of focus during high-risk tasks. Mind mapping helped with convergent thinking and draw relationships between ideas.

As a UX designer, I am familiar with defining project objectives and finding ways to measure those outcomes at each phase. Objectives are measurable mainly by user feedback, testing, and product usage data.

Objectives

Identify specific wearable devices and sensors that will work holistically in the solution. Measure: Identify the research put into each device and the depth of thought in the system. Engineering and software expertise can help determine feasibility of solution.

Brainstorm different solutions and identify the best few ideas. Consider factors such as the level of effort to deliver solution, complexity, financial capacity, and project deadlines. Measure: Gauge the level of effort and depth in each idea. The best ideas will be determined from feedback from the team, the class, and the professor.

Create effective prototypes Measure: Validate each solution against the initial product requirements. Has all the requirements been met?

Test design solutions and iterate for an effective solution Measure: Test the solution for design flaws. Iterate on the solution and test again to reduce design flaws to a minimal. Solution can always be approved upon, but a good measurement is to track the marked improvements between the initial solution and the successive iterations.

After completing my individual problem definition, our group had a Sunday meeting where we discussed the material. It was an excellent way to get everyone on the same page. Everyone seemed to be on the same page and it was easy to see the problem definition come together as a group.

We began to take a step-wise abstraction on the problem definition. First, we were all in consensus that the problem was about innovating in a niche market that has very little assistive technology developed. This market are for those that perform high-risk tasks, such as surgery, mountain climbing, driving a vehicle, EMS dispatchers. There is very little done to monitor the current mental state of the practitioner and guide them to remain focused.

Next, we looked at the project constraints. Each team member had something to add that provided meaningful input. As someone in the software space, I’ve taken project management course in the past and understood that constraints helped to define the scope of the work. Without constraints, there would be a limitless number of solutions. Our team thought about different project management factors such as quality, time management, target market demographic, technological feasibility and cost reduction.

Finally, the team took to the project objectives. We looked at the objectives from two perspectives – the project vision / the ultimate end achievable end-goal and the goal of each project phase. For the project vision, we wanted to achieve a product that had high adoption, since an effective solution with long market adoption is rendered useless. We also want the technology to seamlessly integrate into the subject’s workflow and avoid introduction of a new distraction to their space. We also want the organization that employs this technology to benefit financially, by reducing insurance costs.

Problem Definition (Group)

High-risk environments where physical, mental, and emotional states where harm might be done to people or equipment.

We seek to develop a system that can:

1. Help to develop the operator identify...  1. At-risk states of body and mind  2. Avoidable accidents before they happen  2. Coach them to develop greater emotional resilience and awareness over time  1. How to mitigate factors that may make people more accident-prone  2. Do not rely on training alone.  3. User feels empowered, not monitored (self-monitoring/ownership) 

Constraints

1. Limit to high-risk tasks where it is possible to become complacent: piloting a plane, performing surgery, driving a car/truck, EMS emergency dispatch, high-voltage switching, construction/operating large/heavy machinery  2. Technology must exist or be feasible to create.   3. Initial product concept should be a minimum viable product (MVP)  4. Product should be unobstructive or be incorporated/integrated into the environment. Must be safe (can’t introduce a safety hazard)  5. Necessary mobility of user (as it informs/limits solution)  6. Time and resources.  7. Cost and affordability of product/solution.  8. Our own abilities.  9. Create a product that is widely adopted by the target demographic. This can be achieved through user research. If a product is an effective solution, but has no adopters, it’s useless. 

Objectives identified for current phase:

1. Create a solution that will be useful/sought out/seamlessly integrated.  2. Create a solution that provides effective feedback (that is discreet and not distracting).  3. Team becomes expert in technology used and states being studied/identified.  4. Reduce costs associated with illness and injury – sick time, worker’s comp, malpractice, and insurance rates.  

Objectives for remaining phases:

In the status quo, there are little assistive technologies developed that help improve the user’s focus in such situations. There is room to innovate in this niche. The objective is to develop EEG wearable for risk aversion when a subject performs a high-risk task. This will ultimately improve public safety and advance the industry in safety technology.

Create effective prototypes Measure: Validate each solution against the initial product requirements. Has all the requirements been met?

Conjunction Junction

The Champion Line

My cat, Yuki, is a fluffy, cute, full-grown adult AND very teeny. She is from the mini munchkin breed AND there is another larger Scottish Fold mixed cat, Elmo, that lives in the house. Their play fights are brutal when thinking their sizes AND ferociousness can determine victory.

My cat, Yuki, is a fluffy, cute, full-grown adult BUT very teeny. She is from the mini munchkin breed BUT there is another larger Scottish Fold mixed, Elmo, that lives in the house. Their play fights are brutal when thinking their sizes BUT ferociousness can determine victory.

Two’s Company, but Three’s a Crowd

My housemate is friendly AND works long hours for school and work. We feel we have more space to ourselves, AND we don’t see her often.

My housemate is friendly BUT works long hours for school and work. We feel we have more space to ourselves, BUT we don’t see her often.

USC Day Saturday

Saturday was real work AND tranquil. I got a lot done AND it was quiet with a lot of alone time.

Saturday was real work BUT tranquil. I got a lot done BUT it was quiet with a lot of alone time.

Pizza Sunday

I made a Chicago deep dish pizza from scratch this Sunday. It was delicious, evident in my happy stomach AND fatter belly.

I made a Chicago deep dish pizza from scratch this Sunday. It was delicious, evident in my happy stomach BUT fatter belly.

Mad Men

I work for an ad agency as an app designer AND it doesn’t require my full skill capacity. It’s a low key environment AND too easy. My work doesn’t require the full design process with a more limited specialized scope.

I work for an ad agency as an app designer BUT it doesn’t require my full skill capacity. It’s a low key environment BUT too easy. My work doesn’t require the full design process with a more limited specialized scope.

Morphological Analysis

@warren-usc Peek Into the Inner Charm

@shannondseeger Crowd Pleaser

@well-being-tech Shaping Things

Analysis

I looked at the problem from a micro perspective, based on our vision and how a single user would apply the technology to their everyday use. To do so, I thought about the problem and how I would apply the technology in my own situation. I thought of situations that would require my alertness and calm clear state of mind. I thought about driving a vehicle, and how the EEG wearable might alert me when I’m dosing off. I also thought about other situations, such as being nervous when dating someone and how the EEG wearable can direct you to speak to her in a composed manner. For a more serious case, this EEG wearable can help surgeons who require strong attention to detail and a calm state of mind to operate on a patient. I practiced idea dumping and jotted down all my ideas.

I looked at the problem from a macro perspective, and tried to understand how our target market would use the technology and to see if it’s viable. To do so, I performed a competitive analysis into other EEG wearables, standing on the shoulder of giants. By understanding the current usage of EEG wearables, I was able to discern common usage patterns, validating the viability of our vision. A wearable called Muse Meditation, was a headband that uses EEG sensors to provide feedback to companion phone app. Muse helped the user stay calm and in the correct state of focus for their meditative practice. Another product called NeuroSky measures your brainwaves and senses your attention during meditation. A more ambitious product called Halo Sport, aimed at athletes (amateur and pro), uses neuropriming to stimulate your motor cortex as you workout. This heightens your brain’s plasticity and learning. Basically, it sends pulses of electrical current directly into the wearer’s scalp and into the motor cortex. Similar to Muse, Safilo X is also an EEG wearable, except the product has manifested in the form of smart sunglasses. Safilo X can also track facial expression and eye movement, with the goal to regulate emotions when the user is to perform under pressure. A common pattern for the wearables was the ability to detect alertness and calmness.

I researched EEG scans in general to better understand their applications in medical offices, broadening my perspective. EEG measures electricity produced by the brain and can detect abnormal brainwaves, caused by a head injury, stroke, epilepsy, seizure, dementia, or brain death. Traditionally, EEG cannot pick up on feelings or thoughts. In a 2015 breakthrough research, a commercial EEG wearable called Emotiv was able to detect fluctuations in brain activity when subjects were shown images associated to positive emotions.

Research has led to discovery of a challenge for our product, where EEG wearables will pick up on other electrical signals, the “noise,” such as muscle movement. In labs, scientists provide a controlled environment to reduce the noise by having patients remain motionless. Scientists also use conductive paste to improve the strength of the EEG signals. Modern wearables uses dry electrodes, without the conductive paste, and their accuracy has improved to be on par with wet electrodes. However, researchers still feel that these commercial EEG wearables are mainly picking up on muscle movements rather than EEG signals. To help filter out this noise, commercial EEG wearables are using software to identify true EEG signals.

Through morphological analysis, our team performed attribute listing. Shannon looked at applications for the technology and the target audience. Nelson looked at the sensors and types of hardware we can pursue. From my angle, I looked at how software played a role in the wearable. We can collect the EEG data from all of our users and store it in the cloud. Our machine learning algorithm can learn from the crowdsourced data, improve improve its accuracy and ability to guide. I also looked at how we can use NFC, web development, mobile computing, augmented reality, and analytics. The morphological analysis helped promote divergent thinking and brainstorm new ideas that may never come to fruition.

Contingency Management

Understand your limits. what are your capabilities and the collective capabilities of your team?

@well-being-tech

We have limited time (in terms of calendar days for each stage of the project and in terms of other commitments) and other resources. I think 10 hours (up to 20 hours for extra important steps) is the most I can dedicate to the project per week, since I am already working 60 hours.

@shannondseeger

We all have busy schedules, so there may be challenges with aligning them. Our backgrounds are disparate, which is beneficial in terms of diversity of thought, but we will also have to communicate conscientiously.

@warren-usc

My profession is user experience design, which means I know how to conduct user research and apply it to a design solution. I also have experience with project management and I’ve taken a project management course. On the job, I make use of PM tools like Jira or PivotalTracker to track progress.

Group

We have a diverse set of skills, network, and resources including business (non-profit fundraising, business intelligence, relationship management), design (UX, branding), technology (computer science, utility operations, reliability analysis), networks (e.g. U Maryland, U of Florida, UC Irvine).

Rules of Engagement (i.e. Team Norms)

Always make sure we are notified via text and agree upon a date / time prior to scheduling a meeting

Be responsive

Disagree without being disagreeable: Keep everyone informed if there is a disagreement and discuss it with the team

Make sure everyone is participating and sharing (practice active listening)

Mutual commitment to a high standard of quality and integrity

During divergent process steps, work horizontally in all aspects; During convergent stages, integrate feedback from all parties respectfully, but allow each point person to lead in the area they have the most experience in order to prevent getting stuck

Seek to enjoy the process and have fun

Establish reasonable and feasible goals and standards. What are your and your team’s intentions and are they in line with your abilities. Where does your team have gaps and how will you mitigate that?

@well-being-tech

I think the challenge will be to be fearless with our imagination in the start, but then be disciplined to limit the scope to a realistic and achievable goal for the project that fits within the course. From our discussions, my team’s intention is to tap into our collective experience and resources, to learn from each other and from this creative problem solving exercise, and

@shannondseeger

I certainly have knowledge gaps when it comes to some of the areas we’re about to dig into. I want to be careful to manage the scope and timeline of the project while remaining true to the exploratory, creative spirit of it.

@warren-usc

Our team intends to develop a solution that is innovative and new. This is in line with my capabilities in UX, where we conduct research and prototype a solution.

Group

• Create a general product scope and requirements

• Determine if intended solution is feasible and still exciting after going through process

• Commit to/explore, learn and enjoy the process

• Potential gaps: industrial design, knowledge gaps relating to business and resources, physical distance (needing to communicate digitally for the most part)

Be strict and consistent. Do not promise what you cannot deliver. Talk with your team on how to stay within scope and meet and exceed expectations within your collective means.

@warren-usc

One of the keys to agile development is to avoid scope creep and stick to the original plan. This includes avoiding nice-to-have features and focusing on a minimum viable product with the core features. Once the initial concept has been developed and we have the resource capacity, we can decide on enhancing the product and adding additional features.

@shannondseeger

Though I fully believe in the leader-of-the-moment (whoever is most expert for that portion of discussion), it will be useful to have roles, guidelines, and scope that we can help each other adhere to.

@well-being-tech

I find that having a written scope of work and set of expectations with frequent check-ins is important. Assigning a project manager and domain leads will be helpful to keep us all on track and work through sticky points.

Group

Have a written set of goals and a plan to achieve them and frequent group check-ins to make sure we are sticking to the plan (minimally viable/lovable product)

Reward yourself. What incentives do you and your team value when you meet your goals and, conversely, what is agreed upon and accepted “consequences” for you or your team members not contributing or behaving poorly?

@warren-usc

We are intrinsically driven to help the world with a new tool. By aiding the community, we feel we are making a change and it’s a rewarding experience in of itself.

@shannondseeger

I began this program to learn from projects, professors, and peers. The process itself will be a reward, and our goal is to create something helpful to others, which is always rewarding. If we hold each other and ourselves to a high standard, we shouldn’t have to deal with the consequences of poor behavior. Strong and consistent communication will help as well.

@well-being-tech

I am looking forward to sharpening my skills in the innovation and startup process, learning with expert feedback and insights from my colleagues with other domain expertise. I am investing precious resources into this experience, and want to get the most out of it; I am genuinely passionate about every aspect of our collective prompt; there is an outside chance that the project could inspire a rewarding collaboration beyond the course work. I certainly would not like to disappoint myself, my peers and mentors.

Group

We are intrinsically motivated to go through the process as a rewarding experience of growth and development; the potential reward of obtaining a better understanding of the process and the subject matter; making a real contribution to improve safety and well-being; get the most out of the course experience; no one wants to feel disappointed with themselves, miss out on the opportunity or be perceived in a negative light by peers and mentors due to lack of commitment, progress or conflict.

The Destination and Journey

Team Onspyre

Initial brainstorming

Mindfulness

Safety

Emotional stress

Driving and Traffic

Tech & Innovation

Emergent theme

Using technology (e.g. sensors) and techniques (e.g. mindfulness) to detect at-risk physical, emotional, or mental states while performing a hazardous task (e.g. driving a car, operating a fork-lift, performing high-voltage work)

Roles (Point persons, leadership areas)

We have overlapping areas of expertise, but we can have point persons for each domain:

Design lead: Warren @warren-usc

Business lead: Shannon @shannondseeger

Technology lead: Nelson @well-being-tech

Rationale

@warren-usc

I should be a part of the team, because I have experience prototyping solutions and testing them prior to development. This is important in uncovering the flaws of the design and ensuring it meets project goals. I’m interested in exploring new technology and ways it can impact users. I can contribute my knowledge in the software and design space to help develop an innovative solution.

@shannondseeger

I have experience aligning resources with priorities, tracking goals and metrics, and communicating narratives and ideas. My background in fundraising has given me a foundation in evidence-based decision making, persuasive techniques, and relationship management. I am confident that, with my team, we can manage the timeline and scope of this project to fit within the parameters set for us. I’m looking forward to digging into the wellness, tech, and design aspects of this project.

@well-being-tech

I have worked in hazardous environments for over a decade and have had to learn a good deal about industrial safety and the types of mental, physical and emotional states that put even highly-trained personnel at risk. I have trained, researched and taught mindfulness practices for two decades. I recently got a 9,000-employee entity to incorporate mindfulness into the safety and health (illness and injury prevention) curriculum for all team members. I have attended conferences and given presentations with a focus on the use of technology for safety and well-being. As such, I have awareness of technologies that could be applied or developed to solve our problem/opportunity. I have developed processes, training, and products in related spaces and I am passionate about technological innovation, safety and applied mindfulness.

Trending Blogs

Recently Viewed Blogs

Warren's Process Journal @ USC