Skip to content

Commit 9f63c52

Browse files
committed
update offsites blog
1 parent 6a69772 commit 9f63c52

File tree

1 file changed

+28
-3
lines changed

1 file changed

+28
-3
lines changed

offsites.md

Lines changed: 28 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -155,9 +155,34 @@ following morning allowing people to fly off that afternoon (or stay the extra
155155
day in the beautiful location).
156156

157157

158+
Mix Structured and Unstructured Time
159+
------------------------------------
160+
161+
I abhor waste due to scheduling. As a result I typically run a pretty tight
162+
event. This means tracking everyone's work, redirecting people, staying on
163+
task, and breaking up large meandering conversations.
164+
165+
Eventually the attendees rebel, and rightly so. It's also important to build
166+
in some unstructured time for folks to explore on their own. This happens
167+
naturally in the mornings and evenings, but it's also ok to spend an afternoon
168+
on intentionally unstructured efforts.
169+
170+
158171
Invite Visitors
159172
---------------
160173

161-
Investors or collaborators in the area may want to join for a time. I'd
162-
encourage you to start the first day with just the team, but adding people over
163-
time can be energizing.
174+
Investors, collaborators, or ex-teammates in the area may want to join for a
175+
time. I'd encourage you to start the first day with just the team, but adding
176+
people over time can be energizing.
177+
178+
Feedback
179+
--------
180+
181+
It's good to get feedback from the team so that you can iterate and improve.
182+
I've done this in two ways:
183+
184+
1. Send a form afterwards (google forms is simple) with a couple of simple
185+
questions like "What did you like?", "What could improve?", and "Other
186+
suggestions?" with an option to add your name
187+
188+
2. Spend ten minutes at the end of the offiste discussing things as a group.

0 commit comments

Comments
 (0)