Here’s a cool side project I’m working on using AI to help skiers, snowboarders, and bikers get the best price on their gear. Add a product to your watchlist, Wacka will find it on other sites and alert you anytime the price drops on any of the sites. https://t.co/l264HUOTFq
@fsmKeenan@USPS Our USPS is brutal. Stuff comes open, goes to our neighbors, theirs comes to us… don’t know if it’s a problem everywhere or just smaller mountain communities but it’s bad!
- start with wireframes and get your information hierarchy down.
- once stakeholders are satisfied, turn these into designs.
- not all designers are created equal. Also, ensure you have an expert in UI/UX and not just a good graphic designer. …very different skillsets.
Back to System Design & Planning. Once you’re through the workflows phase, it’s a good time to bring in your UI/UX specialists to start building out wireframes.
These wireframes (and eventually designs) will be a visual culmination of the work and artifacts to date.
We’ll put the conversation around design and planning on hold this week. Who you got for the natty Monday night? As a Buckeyes fan, after several years of heartbreak I think this is the year they get it done.
Next phase of System Design & Planning is the creation of Technical Workflows…
We pick out the most impactful workflows along with all of the areas that need more eyeballs to ensure the desired UX.
- Define step by step process to navigate the system
- Navigate major inputs, outputs, dependencies, and interactions between components
- Aids in understanding system architecture and integration points.
System Design & Planning Cont’d…
After the Epic to Feature is complete, it’s a good time to go through a Lean Canvas exercise.
- Takes the client through clearly articulating everything from Problem and Solution to Value Prop and Revenue streams.
- This is often as beneficial to the client as it is to the product team
- There are always nuggets that come to light through this session that help inform product and development.
System Design & Planning for a new software build cont’d…
Once discovery is complete, the next step is creating the first artifact… the Epic to Feature Map.
We use @LucidSoftware but any post it note application will do. Here you start digesting discovery…
- the teams software design expertise and experience starts to mold business requirements into software reqs, system logic, interaction design, etc
Can’t stress this enough - your product lead should be setting clear and proper expectations through every phase of the process.
Picking up on System Design & Planning after the turkey break. Some thoughts on kicking off a productive discovery phase..
1) I like to bring in all key stakeholders here for a variety of needs and perspectives from the client side
…surface questions and clarification around your business model as well. If your discovery phase doesn’t challenge your business model or processes - you should be looking for a new team