This document discusses solution design meetings for remote teams. Solution design meetings allow team members to discuss risks, constraints, requirements, and expected outcomes of solutions being built. This builds shared understanding of the product and adds accuracy to the development process over time. The document also discusses how remote teams can achieve "osmotic communication" by using collaboration tools that allow information to flow between team members like public discussions and notifications. It suggests these tools help remote teams pick up relevant information similar to being in the same physical room.

1. How to Effectively
Work with Remote Teams
An Introduction to Solution Design Meetings

2. Topics
What is Solution Design?
Creating Shared Understanding
Case Study
Anthony Cintron
Co-Founder, CEO

3. The cocktail party effect is the episode of being able to
focus one's auditory attention on a specific stimulus while
filtering out a range of other stimuli.
Partygoers can focus on a single conversation in a noisy
room.] This effect is what allows most people to "tune into" a
single voice and "tune out” others.
A similar phenomenon that occurs when one detects words
of interest originating from unattended stimuli, for instance
hearing one's name in another conversation

4. Osmotic communication means that information flows into the
background hearing of members of the team, so that they pick
up relevant information as through by osmosis.
This is normally accomplished by seating teams in the same room.
When one person asks a question, others in the room can either
tune in or tune out, contributing to the discussion or continuing
with their work

5. Solution design meetings are forums where team members
have an opportunity to discuss risks, constraints, conditions and
requirements. The outcome is deeper understanding of what is
expected to be built, and why we’re building a particular solution.
Over time these proposed solutions accumulate and build deeper
stories for future sprints. The team increases awareness of the
product’s pervasiveness. This in return adds accuracy and
effectiveness to the development process.

6. Studies have indicated that less than
30%of a programmer’s
time is spent on traditional coding tasks and less than 20%
of the time is spent on coding.
Rest of the time is spent in meetings, problem resolution with
the team, resolving issues with customers, product testing, etc.

8. OpenStile.com Journey Mapping, July 2016

10. • High-fidelity
design
• UX testing
• Designer
synchronization
Effective Remote Collaboration Tools
• Public ad-hock
discussions
• Notifications/
Invites
• Metric Reports
• Documentation
• Research
Summary
• Issue
tracking
• Project
Management
• Tracability
Matrix
• User Mapping
• low-fidelity
design
• Realt-time
visualization

11. • Story behind the photo is missing
• You may know, but you may not understand
What’s most important isn’t what’s written down —
it’s what we remember when we read it.
Good Documents Are Like a Poor
Instagram Pic

13. What is it?
Frame Your Idea
Why build it?
Priority
Desired outcome
What problem
does it solve?
Tell me about the
benefits for you
and for the
people who will
use this.

14. Contact
acintron@untangl.co
Instagram
@antocintron