There is an opportunity here to bridge the hardware and software side of things and work on an actual project. As Greg’s mentioned, it’s a good approach to learning and applying new skills.
My original idea in proposing a design skills workshop was to look at the challenges of UX design for connected/embedded devices (as opposed to designing for a software only context). So things like creating flows and documentation for device discovery and pairing with a mobile phone/application, network and device configurations, device status, syncing data, etc.
To this end, I propose the following:
Self-organise in small groups of 4-5 people. Teams can either be hardware design, or mix of hardware/software design (I’m assuming that there are more hardware than software folks but I could be wrong). Each team chooses what they want to work on. If there are only a few UX folks, we can float between teams and create documentation.
If there are less than 10 people, attending the workshop, then we can work on one project and organize based on specific skills. Personally, I’d love to work on a prototype where we design a wireless open source smart thermostat that measures humidity and room temperature (maybe one that could even be a gateway to a distributed grid ). But I’m totally open to anything.
For the UX stuff, I can go through the steps in a product journey: 1) writing user stories (focusing on empathy); 2) creating wire-frames / flows of features decided by team; and 3) designing basic interface and/or clickable prototype.
Let me know what you all think so that I could formalize this and apply for the design skills share.