@javeaisgreat it was great discussing with you. Here are my notes. I have to confess one thing: the idea about framing the shadowing session as a pair programming session came during our conversation!
- Discuss the non-profit aspect in the user research: there is money but be transparent about it
- Comments regarding the current pitch:
- fedeproxy is going to allow free software developers to easily move from one software development environment (which we call forge) to another.
- the first phrase must clearly explain what the project is about: building briges between software forges for communicate
- mail = gmail = thunder bird = communicate
- forge = issues = cannot communicate
- example of impact in my work = i cannot record a bug in the other forge
- fedeproxy helps forges to be connect and communicate
- !! building bridges !!
- adding something related to diversity (fedeproxy does not have diversity and is proactively working to fix it)
- lack
- intention
- work 5%
- accountability
- links to diversity category
- the means of communications have a shape (not one shot, more continuous, for instance)
- humanize - relax - social behavior
- Shadowing session
- Get the upper body language
- Write down the introduction
- List of things you want to identify
- List of questions if things do not happen naturaly
- Shadowing framed in a way of pair programming - rubber duck debugging.
- Since this is new, it makes sense to run a pilot before doing the real thing, just to make sure there are no roadblocks