07:00:32 RRSAgent has joined #chairing 07:00:32 logging to http://www.w3.org/2014/06/17-chairing-irc 07:00:33 Zakim has joined #chairing 07:00:46 Zakim, this will be 24873 07:00:46 ok, koalie; I see Team_ChTr()4:00AM scheduled to start in 60 minutes 07:01:37 koalie has changed the topic to: 17-Jun Chair Training: Human Dimension (chaals) https://www.w3.org/wiki/Guide/HumanDimension 07:03:26 chaals has joined #chairing 07:23:38 agenda? 07:23:54 agenda+ introductions (<1 min please) 07:24:16 agenda+ Group Dynamics - fatigue, timing 07:24:58 agenda+ The chair 07:25:42 agenda+ what if we reconsider… - decisions 07:27:12 agenda+ what next? 07:55:13 nigel has joined #chairing 07:57:25 Team_ChTr()4:00AM has now started 07:57:32 +[IPcaller] 07:57:55 zakim, [ip is me 07:57:55 +chaals; got it 07:58:17 yosuke has joined #chairing 07:58:30 +nigel 07:59:08 Present+ Nigel 07:59:17 Chair: Chaals 07:59:35 rrsagent, make log public 07:59:40 +??P2 07:59:59 kerry has joined #chairing 08:00:01 zakim, ??p2 is Lisa 08:00:01 +Lisa; got it 08:00:19 LisaSeeman has joined #chairing 08:00:20 Present+ Lisa 08:00:41 scribenick: koalie 08:00:49 gmandyam has joined #chairing 08:01:02 +koalie 08:01:03 Andy has joined #chairing 08:01:14 xiaoqian has joined #chairing 08:01:23 +[IPcaller] 08:01:23 present+ 1-Coralie 08:01:48 zakim, [ip is yosuke 08:01:48 +yosuke; got it 08:01:58 zakim, call xiaoqian-mobile 08:01:58 ok, xiaoqian; the call is being made 08:02:00 +Xiaoqian 08:02:02 present+ 1-Yosuke 08:02:12 + +61.4.097.8.aaaa 08:02:33 zakim, aaaa is Kerry 08:02:33 +Kerry; got it 08:02:41 Present+ 1-Kerry 08:02:53 +gmandyam 08:03:03 +[IBM-Hursley] 08:03:11 present+ 1-Giri 08:03:22 zakim, [IBM is me 08:03:22 +Andy; got it 08:03:23 mute me 08:03:34 zakim, mute lisa 08:03:34 Lisa should now be muted 08:05:18 present+ 1-Cindy 08:05:35 Zakim, agenda? 08:05:35 I see 5 items remaining on the agenda: 08:05:36 1. introductions (<1 min please) [from chaals] 08:05:36 2. Group Dynamics - fatigue, timing [from chaals] 08:05:36 3. The chair [from chaals] 08:05:36 4. what if we reconsider… - decisions [from chaals] 08:05:36 5. what next? [from chaals] 08:05:42 Zakim, take up item 1 08:05:42 agendum 1. "introductions (<1 min please)" taken up [from chaals] 08:06:00 Chaals: We may be recorded, if you do not wish your comment to be recorded, please, write /me in IRC 08:06:03 Zakim, close this item 08:06:03 agendum 1 closed 08:06:04 I see 4 items remaining on the agenda; the next one is 08:06:04 2. Group Dynamics - fatigue, timing [from chaals] 08:06:07 Zakim, next item 08:06:07 agendum 2. "Group Dynamics - fatigue, timing" taken up [from chaals] 08:06:21 Andy_Coleman: XML Query WG co-chair, recently appointed 08:06:37 Giri: Geolocation WG co-chair, recently appointed 08:07:18 zakim, unmute lisa 08:07:18 Lisa should no longer be muted 08:07:26 Kerry_Taylor: SSN XG a couple years ago, will be appointed @@ in the future 08:07:39 s/@@/to a new WG/ 08:07:45 Lisa_Seeman: @@ accessibility 08:07:56 Nigel_Megitt: co-chair Timed Text WG 08:07:59 zakim, mute lisa 08:07:59 Lisa should now be muted 08:08:10 Cindy: Team Contacts of Web Apps WG 08:08:15 s/@@/TF on cognitive 08:08:24 Yosuke_Funahashi: Co-chair of Web and TV IG 08:08:36 zakim, take up agendum 2 08:08:36 agendum 2. "Group Dynamics - fatigue, timing" taken up [from chaals] 08:08:37 Zakim, close this item 08:08:37 agendum 2 closed 08:08:38 I see 3 items remaining on the agenda; the next one is 08:08:38 3. The chair [from chaals] 08:09:03 -> https://www.w3.org/wiki/Guide/HumanDimension The driving document 08:09:10 Topic: Group Dynamics - fatigue, timing 08:10:32 chaals: I chose fatigue and timing topics on purpose 08:11:02 ... hard to concentrate more than one hour 08:11:08 ... you can take small breaks 08:11:18 ... I plan to take a break after one hour into this call 08:11:28 ... We may use or not the second hour 08:11:33 ... But we'll take a break 08:11:39 ... No-one is forced to take a break 08:11:54 ... I hope to stop after an hour 08:12:01 ... I use that break A LOT 08:12:22 ... We often find that groups get wound up on details and lose focus 08:12:33 ... When I chair meetings, I reset the focus on the agenda 08:12:58 ... My experience is that if people have not found agreement in one hour, they're unlikely to find it for an hour and 15 minutes and so on 08:13:17 ... If people are close to agreement, I find that either during the break, or that evening, they solve the problem on their own 08:13:29 ... and next time we have the discussion we find we've come to consensus. 08:13:37 q? 08:13:55 chaals: I hope not to be giving a lecture for an hour; please do use the queue 08:14:15 Topic: The Chair 08:14:42 chaals: A lot of the things I know about chairing I learned by sitting in meetings and watching chairs 08:14:55 ... and thinking at time "oh, if I'm chair, I don't want to do this" 08:15:20 ... It's valuable to collect lists of "don't do that" 08:15:32 ... Are there things that Chairs do that drive you nuts? 08:15:38 ... speak up 08:15:46 q+ 08:15:50 ack nigel 08:16:02 q+ to say "replying to each speaker, before the next person in queue gets to say anything" 08:16:11 Nigel: When a chair allows someone to talk for too long without giving much information 08:16:14 ack me 08:16:14 chaals, you wanted to say "replying to each speaker, before the next person in queue gets to say anything" 08:16:16 chaals: Yes 08:16:32 chaals: One of the things I find annoying is a chair that replies to every speaker 08:16:49 chaals: it takes a lot of time and isn't always useful 08:17:06 q+ 08:17:07 q+ 08:17:12 ack and 08:17:13 ack andy 08:17:41 Zakim, lisa is me 08:17:41 +LisaSeeman; got it 08:17:42 Andy: Outside W3C I've experienced a chair @@not very helpful for getting things done 08:17:54 ack lis 08:18:05 s/@@/monstering the group and acting more like a president than a chair / 08:18:38 Lisa: One of the things that bug me is when something from previous meetings comes up again dispite this having been minuted and the chair lets the re-hashing happen 08:18:43 ... chair should give orientation 08:18:59 s/dispite/despite/ 08:19:04 ... and suggest to revisit only if there are issues 08:19:10 zakim, mute lisa 08:19:10 LisaSeeman should now be muted 08:19:12 Experiences a chair that acts as a President with advisers rather than as an 'equal' as far as decision making is concerned 08:19:15 q? 08:19:16 zakim muke me 08:19:43 q+ to complain about chiars who don't know the tools 08:19:48 ack me 08:19:48 chaals, you wanted to complain about chiars who don't know the tools 08:20:06 chaals: Another frustration is about Chairs unaware of tools we have, and how to use them 08:20:22 -> http://www.w3.org/2014/Talks/0423-tools-rrs/#(1) W3C tools for chairs (last chair training session) 08:20:36 chaals: Here's a link to Ralph's tools session in previous chair training 08:21:01 chaals: Also, chairs who don't manage to keep the agenda 08:21:38 chaals: I'm happy with changing an agenda during the meeting, but it can be frustrated when you travel or get up at 3 in the morning and an agenda is hi-jacked 08:21:50 ... agenda needs to be fair to anybody 08:22:18 chaals: There are other things that Chairs do wrong, and we, I in particular, are humans and volunteers; it's not surprising we don't get everything right 08:22:24 ... but it's important we try to set an example 08:22:31 ... I will come back to the topic perhaps 08:22:42 ... There is another part of the difficulty: giving your own opinion 08:22:51 Topic: Giving your personal opinion 08:23:07 chaals: in a WG, we are possibly our company's representative 08:23:31 ... balancing the way we chair the group and the way we represent our own perspective is quite difficult 08:23:46 chaals: Andy, you mentioned a chair 08:24:10 Andy: Yes, in a government body, supposedly organised the same way; the chair thought himself as the leader 08:24:17 ... and dismissed opinions 08:24:35 chaals: One of the issues is that chairs reasonably have strong personality 08:24:47 ... they're appointed because they're deemed to be able to leading the group 08:24:53 ... How to balance that? 08:24:56 q+ 08:24:59 q+ 08:25:14 Nigel: So far, I've tried to stay quiet as long as possible 08:26:06 q+ to say I try to use the queue strictly, especially on myself. 08:26:10 ack ni 08:26:19 ... treading the tricky line between summarising and telling what the decision is 08:26:29 ack li 08:26:46 】【‘ 08:26:59 Lisa: what I try to remember to do is to say when I'm speaking my opinion as a member of the group 08:27:13 s//】【‘/ 08:27:28 ack me 08:27:28 chaals, you wanted to say I try to use the queue strictly, especially on myself. 08:27:32 Lisa: At the end of the conversation, I ask if anyone would like to comment@@ 08:27:36 zakim, mute me 08:27:36 LisaSeeman should now be muted 08:27:36 mute li 08:27:57 chaals: I do something similar and use the queue strictly 08:28:12 ... I try to distinguish me giving an opinion and me being chair 08:28:31 ... this goes back to what Nigel said, trying to make resolutions really clear 08:28:49 ... the difference between providing and being chair: I'll try to clarify what people have said 08:29:18 ... I'll do that as an individual, but if we're reaching a conclusion point, I'll try to reach a resolution 08:29:31 ... a statement that people can agree, or disagree with 08:29:59 ... write that down as a clear resolution; separately from the things I said as a member of the group 08:30:21 kerry has left #chairing 08:30:23 ... Chairs who don't clearly state the things we agreed to do so you can't object is a problem I've had with a number of chairs 08:30:36 s/can't/can/ 08:30:52 Zakim, agenda? 08:30:52 I see 3 items remaining on the agenda: 08:30:53 3. The chair [from chaals] 08:30:53 4. what if we reconsider… - decisions [from chaals] 08:30:53 5. what next? [from chaals] 08:31:00 Zakim, take up item 4 08:31:00 agendum 4. "what if we reconsider… - decisions" taken up [from chaals] 08:31:04 Zakim, drop item 3 08:31:04 agendum 3, The chair, dropped 08:31:15 chaals: This is the point that Lisa mentioned 08:31:27 ... How do you get a group to make a decision? 08:31:31 ... this is really tricky 08:31:37 ... as Nigel said, chairing is difficult 08:32:08 ... the cracks of what is difficult, when the goas is to get consensus, if how to get consensus as opposed to discussing forever 08:32:12 s/goas/goal/ 08:32:16 q+ 08:32:26 ack lisa 08:32:29 ... and how Lisa mentioned, to prevent re-hashing past discussion 08:32:45 Lisa: Our 1st deliverabal: gap analysis 08:32:53 s/abal/able/ 08:32:54 ... what can be done to help people have better access to the Web 08:33:12 ... for such a vast topic, there are numerous topics 08:33:21 kerry has joined #chairing 08:33:21 ... Also, educating the group 08:33:44 Lisa: issues on a document, summary of different technologies, so people can refer back to them 08:33:49 ... we use wiki a lot 08:34:18 q+ 08:34:35 Lisa: Any topic that comes up I try to make sure there's a logical place on the wiki to save it 08:34:43 q+ to say we set a 10 day post-resolution 'cooling off' period 08:34:47 Lisa: so people ought to be on the same page 08:34:49 q- later 08:35:08 Lisa: Also, I give my group my @@ and try to be available for them, especially for newbies 08:35:20 s/@@/Skype handle etc 08:35:25 zakim, mute me 08:35:25 LisaSeeman should now be muted 08:35:25 ... people can re-open discussion, but often they need to be filled in. 08:35:31 ack n 08:35:31 nigel, you wanted to say we set a 10 day post-resolution 'cooling off' period 08:35:34 q- 08:35:48 Nigel: We have a statement in our charter that I often reiterate 08:36:17 Nigel: There is a ten-day period after resolutions are made that allows people to object, catch up, raise issues, etc. 08:36:24 Nigel: That's another tool 08:36:38 [enabling email decisions] 08:36:45 q+ 08:36:56 q+ 08:36:58 Nigel: if people are late, I can use this tool (I have yet to) 08:37:00 ack ch 08:37:11 chaals: as an AC rep, I object to charters which do not enable that 08:37:20 chaals: I think it's a great tool. 08:37:48 ack kerr 08:37:49 chaals: The ability to stop recycling discussion depends on having things written clearly written, and in obvious places, like Lisa said. 08:37:52 ack k 08:38:03 Kerry: I have to leave, thanks very much! 08:38:03 -Kerry 08:38:08 chaals: Thanks for coming! 08:38:11 q+ 08:38:23 [Kerry Taylor leaves] 08:38:24 ack ch 08:39:01 chaasl: I had not heard the cooling off expressed as such as Nigel mentioned it. And writing things down makes sense. 08:39:10 ... there's another side of recycling discussion 08:39:17 ... when someone brings a new perspective, 08:39:32 q+ to say that with issues we sometimes close them off and then allow new issues to be raised against the resolution in the previous issue 08:39:39 ack ni 08:39:39 nigel, you wanted to say that with issues we sometimes close them off and then allow new issues to be raised against the resolution in the previous issue 08:39:43 ... is there a way, any tool (other than memory) to highlight it as new perspective? 08:39:46 ack ni 08:40:19 Nigel: We sometimes close issues and a new issued is raised on a solution that closed a previous issue 08:40:21 q+ 08:40:35 ... It created a multi-layer thing and makes it a bit harder for the Chair 08:40:42 s/created/creates/ 08:40:58 Nigel: Very often it's a new thing that somebody thought of. 08:41:03 ack me 08:41:11 chaals: I like that, actually 08:41:23 ... one of the thing that's attractive is that it lets you close issues 08:41:32 ... but provides a way to @@ 08:41:44 s/@@/go back to the original discussion 08:41:50 ... so when you go back to the discussion you can go back to the old discussion. 08:42:30 Zakim, agenda? 08:42:30 I see 2 items remaining on the agenda: 08:42:31 4. what if we reconsider… - decisions [from chaals] 08:42:31 5. what next? [from chaals] 08:42:46 q+ 08:42:48 Zakim, close item 4 08:42:48 I see a speaker queue remaining and respectfully decline to close this agendum, koalie 08:42:51 ack li 08:43:02 Zakim, next item 08:43:02 agendum 5. "what next?" taken up [from chaals] 08:43:32 q+ to suggest "I don't need your input" as a topic 08:43:41 Lisa: Having people to create the deliverable they signed up for, in time or not too late, is really hard 08:43:45 ack me 08:43:45 chaals, you wanted to suggest "I don't need your input" as a topic 08:43:52 zakim, mute me 08:43:52 LisaSeeman should now be muted 08:44:52 chaals: How do we use the next 15 minutes into this hour? 08:45:03 agenda+ Meeting timelines with volunteers 08:45:20 chaals: going one by one. 08:45:54 Zakim, agenda? 08:45:54 I see 2 items remaining on the agenda: 08:45:55 5. what next? [from chaals] 08:45:55 6. Meeting timelines with volunteers [from chaals] 08:45:59 Zakim, close this item 08:45:59 agendum 5 closed 08:46:00 I see 1 item remaining on the agenda: 08:46:00 6. Meeting timelines with volunteers [from chaals] 08:46:07 Zakim, take up item 6 08:46:07 agendum 6. "Meeting timelines with volunteers" taken up [from chaals] 08:46:12 q+ 08:46:13 chaals: I'd love a solution to this! 08:46:16 ack n 08:46:20 q+ to add a problem... 08:46:31 Nigel: I've had this problem recently; two deliverables with overlapping timelines 08:46:48 ... different people more keen to progress on one more than the other deliverable 08:47:02 agenda+ Editors who don't listen to the group 08:47:06 ... I've begun a standard practice at every meeting to prioritise agenda items 08:47:21 ... when I do that, people who're keen on something want to bump things up the queue 08:47:34 ... our problem is that we don't have enough time 08:47:45 ... we break the one-hour rule, as a result 08:47:53 ... next time, I'll suggest we have a break after 1 hour 08:47:58 agenda+ action reviews and similar "admin-heavy/traditional" approaches 08:48:14 ... slightly tangantial: when people commit to a timeline and don't deliver output to meet that 08:48:20 ... is there anything that can be done? 08:48:29 q? 08:48:43 ack me 08:48:43 chaals, you wanted to add a problem... 08:48:50 ... waiting for something be be more perfect? or bring down the axe and publish? 08:49:22 chaals: recently, it took 6 months to deliver 3 days of work, but I didn't have 3 days until finally I got it done 08:49:42 ... the problem with "let's ship now" is if you are too strict in applying that, people will ignore what you've done 08:49:56 ... there is a real judgement to make 08:50:34 ... one approach we've tried with some success: offer to other people to help edit a spec and move it forward 08:51:00 q? 08:51:02 q+ 08:51:07 ack li 08:51:07 ... the problem with that is you had a problem and may end up with two problems 08:51:46 Lisa: I've tried to ask for a draft in 6 weeks for something we want to publish in 3 months 08:52:02 ... a 6-week deadline for a chunk is doable 08:52:03 q+ to +1 this idea of small manageable chunks, and then talk about balancing busy people and deliberate blocking 08:52:12 ... you can't ignore a 6-week deadline. 08:52:13 ack me 08:52:13 chaals, you wanted to +1 this idea of small manageable chunks, and then talk about balancing busy people and deliberate blocking 08:52:16 zakim, mute me 08:52:16 LisaSeeman should now be muted 08:52:28 chaals: Breaking it down into manageable sized pieces is something I like a lot 08:52:49 chaals: I'd be interested to know more about how do you find that work or not 08:52:57 chaals: Another snenario: 08:53:19 ... sometimes you have busy peopls, and sometimes in controversial groups, people going to the group just to block the work 08:53:41 ... volunteers on one hand, and people trying to block progress on the other 08:53:58 ... taking up work, requesting extensions and blocking the group for months 08:54:04 ... How do you tell the difference? 08:54:08 ... and, what do you do? 08:54:19 q+ 08:54:22 ack n 08:54:22 ack ni 08:55:03 Nigel: the only way to find out whether they're busy or blockers is to know them 08:55:07 ... talk to them outside of meetings 08:55:20 ... the two behavious seems to be undistinguishable. 08:55:22 q+ 08:55:25 s/vious/viours/ 08:55:29 ack ch 08:55:35 chaals: Knowing the people is really helpful 08:55:41 s/know them/know them as individuals 08:55:51 ... Frankly, I, as a Chair, just make judgement calls. 08:56:13 ... Figuring out what's going on depends on knowing people and their goals 08:56:22 ... tools I use to get closure is impose deadlines 08:56:32 ... problem I have is: it's easy to be seen as unfair 08:56:44 ... in some cases, I'm more or less strictly imposing the deadline. 08:57:04 .. or the group does, based on the general impression 08:57:07 q+ 08:57:15 ... That works unless people start stacking the group. 08:57:33 ... one of the issues I mentioned already: if you impose deadlines too strictly, you lose the people that you really want 08:57:43 chaals: That's one of the things I throw in the balance 08:57:51 ack li 08:57:58 ... I don't have an answer, but how fast do you need to enforce a decision? 08:58:00 agenda? 08:58:27 Lisa: One thing seems to be effective: I switched people around 08:58:59 ... putting a person who's done their part really well on another part 08:59:24 ... there were lots of good reasons to do it in any way, but it may be helpful generally and for more deliverables 08:59:35 q+ time check - do we want to do a second half? 08:59:38 zakim, mute me 08:59:38 LisaSeeman should now be muted 08:59:40 q? 08:59:57 chaals: we've been going on for 55 minutes 09:01:00 chaals: let's take 5 or 10 minutes 09:01:04 ... and resume for a second half 09:01:10 ... I want 10 unless people want 5 09:01:39 ... let's reconvene in 9 minutes. 09:01:41 RRSagent, make minutes 09:01:41 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 09:01:55 agenda+ people who work outside the group 09:02:16 agenda+ ignoring the chair / chairing from the floor 09:06:41 -yosuke 09:08:30 +[IPcaller] 09:11:06 Q+ 09:11:11 -nigel 09:11:26 Zakim, agenda? 09:11:26 I see 5 items remaining on the agenda: 09:11:28 6. Meeting timelines with volunteers [from chaals] 09:11:28 7. Editors who don't listen to the group [from chaals] 09:11:28 8. action reviews and similar "admin-heavy/traditional" approaches [from chaals] 09:11:28 9. people who work outside the group [from chaals] 09:11:28 10. ignoring the chair / chairing from the floor [from chaals] 09:11:30 ack lisa 09:11:42 agenda+ starting on time, and other timing issues 09:11:45 Lisa: on blockers 09:11:57 +nigel 09:12:20 ... if you have serious blockers and if you have an issue, a fantastic tool: make a task force on fixing that issue 09:12:51 ... if you've got your one or two people who block in that TF, the environment is going to be hostile for them 09:13:03 +nigel.a 09:13:18 zakim, mute me 09:13:18 LisaSeeman should now be muted 09:13:25 Zakim, close this item 09:13:25 agendum 6 closed 09:13:26 I see 5 items remaining on the agenda; the next one is 09:13:26 7. Editors who don't listen to the group [from chaals] 09:13:29 Zakim, take up item 11 09:13:29 agendum 11. "starting on time, and other timing issues" taken up [from chaals] 09:13:49 chaals: There's no magic: the chair needs to be there on time 09:14:01 zakim, who is making noise? 09:14:15 chaals, listening for 13 seconds I heard sound from the following: chaals (93%) 09:14:47 ... people are going to be there so respect this 09:15:13 chaals: taking breaks is useful as we've stated earlier 09:15:27 ... how to get people to start on time? 09:15:52 agenda? 09:15:59 ... start and expect late comers to know you start on time so they'd better be on time 09:16:05 q+ 09:16:06 ... end on time too 09:16:10 ack ni 09:16:26 Nigel: stopping on time is something I'm keen on too 09:17:06 ... I've found it doesn't seem reasonable to stop people when they have something to say 09:17:33 s/stop people/start discussions when absent people 09:17:47 s/when they/ 09:18:25 q+ 09:18:32 Andy: Generally, people start arriving on the call and it's 4 or 5 minutes into the call when all have arrived 09:18:34 ack me 09:19:08 chaals: Most of us I suspect rely on calendars and stuff start and end at the top and bottom of the hours 09:19:28 ... if you planned to start at 5 past, would that make people to actually start at 5 past? 09:19:40 ... counting time for people to make transition. 09:19:55 Zakim, agenda? 09:19:55 I see 5 items remaining on the agenda: 09:19:56 7. Editors who don't listen to the group [from chaals] 09:19:56 8. action reviews and similar "admin-heavy/traditional" approaches [from chaals] 09:19:56 9. people who work outside the group [from chaals] 09:19:56 10. ignoring the chair / chairing from the floor [from chaals] 09:19:56 11. starting on time, and other timing issues [from chaals] 09:20:07 Zakim, close this item 09:20:07 agendum 11 closed 09:20:08 I see 4 items remaining on the agenda; the next one is 09:20:08 7. Editors who don't listen to the group [from chaals] 09:20:10 Zakim, take up item 7 09:20:10 agendum 7. "Editors who don't listen to the group" taken up [from chaals] 09:20:29 chaals: This is a bug bear or mine 09:20:46 ... one thought is to replace editors 09:20:57 s/or mine/of mine/ 09:21:07 ... but people who tend to not listen the group are likely to @@ 09:21:15 q+ 09:21:19 ack ni 09:21:24 ... and people who are nominated editors are usually good at that 09:21:44 Nigel: I'd present the edits, and encourage other members to work on proposal for changes 09:21:48 s/likely to @@/relatively likely to just take their toys and leave.../ 09:22:01 ... on wiki so that everyone can see and all have a chance to make changes 09:22:07 zakim, who is here? 09:22:07 On the phone I see chaals, LisaSeeman (muted), koalie (muted), Xiaoqian, gmandyam, Andy, [IPcaller], nigel, nigel.a 09:22:09 On IRC I see xiaoqian, Andy, gmandyam, LisaSeeman, yosuke, nigel, chaals, Zakim, RRSAgent, koalie, schuki 09:22:21 zakim, who is making noise? 09:22:35 LisaSeeman_ has joined #chairing 09:22:35 chaals, listening for 13 seconds I heard sound from the following: chaals (70%) 09:22:38 Nigel: The problem is that sometimes it's easier to edit directly and not look at the wiki 09:23:03 chaals: I don't have a very good answer for this 09:23:46 ... but what I try to point out is that there's a legal reasons at W3C to avoid breaking; anti-competitive behaviour law 09:24:18 ... reminding editors of that is sometimes useful 09:24:38 zakim, drop nigel 09:24:38 nigel is being disconnected 09:24:40 -nigel 09:25:11 Zakim, close this item 09:25:11 agendum 7 closed 09:25:13 I see 3 items remaining on the agenda; the next one is 09:25:13 8. action reviews and similar "admin-heavy/traditional" approaches [from chaals] 09:25:15 zakim, take up agendum 9 09:25:15 agendum 9. "people who work outside the group" taken up [from chaals] 09:25:15 Zakim, take up item 9 09:25:16 agendum 9. "people who work outside the group" taken up [from chaals] 09:25:41 \me what to do about long time getting people identified in zakim? 09:25:47 chaals: people who work outside the group: is it a problem --editors in particular-- and if so, what should we do? 09:26:20 chaals: often we'll cut off the discussion because an hour has gone, people will come back with an answer 09:26:30 ... that's sort of working outside the group 09:27:00 ... we're back to the anti-competitive law 09:27:22 ... if people come back to the meeting and there's a chance for the group to discuss the solution, change it if people are unhappy, I think we're ok with that 09:27:47 ... When I find it a genuine problem is when two or three people don't bother presenting results and changes to the group at all 09:28:07 ... it is harder to track who contributed what 09:28:16 ... in w3C Chairs are expected to track contributions for 09:28:29 s/for/for IPR reasons/ 09:28:36 s/w3C/W3C/ 09:29:04 ... I'm not sure what strategies people have. 09:29:10 ... or even if they consider it a problem 09:29:14 q+ 09:29:17 ack nigel 09:29:17 ack ni 09:29:30 Nigel: I do consider it a problem. But I don't have a strategy. 09:29:47 ... when a doc has been used as basis for a W3C rec and has largely been made outside of W3C 09:30:03 ... it's difficult to uncover information 09:30:19 ... not sure it's a problem if members of the group agree on it? 09:30:38 chaals: You don't have to conclude that if you're a member of@@ 09:31:26 s/@@/ the group, as well as a chair/ 09:31:39 chaals: dirty tricks like going to the webplatform.org team, seeking if it's implementable, helps assess if the basis is good enough. 09:32:05 chaals: for me it's one of the big issues that I face 09:32:34 chaals: I try to encourage a culture of organising meetings, semi-formal dicussions 09:33:09 agenda+ organising meetings 09:33:17 Zakim, close this item 09:33:17 agendum 9 closed 09:33:18 I see 3 items remaining on the agenda; the next one is 09:33:18 8. action reviews and similar "admin-heavy/traditional" approaches [from chaals] 09:33:20 agenda? 09:33:35 Zakim, take up item 10 09:33:35 agendum 10. "ignoring the chair / chairing from the floor" taken up [from chaals] 09:33:57 chaals: in the wiki there were a few things about this topic 09:34:16 chaals: my feeling is that it's not much of a problem if the meeting runs itself; it's a good thing 09:34:29 ... where people just refuse to listen to the Chair, that's much more difficult. 09:34:36 ... I wonder, how do you deal with that? 09:35:07 ack me 09:36:12 chaals: Coralie said you can bring up to the domain lead someone that is difficult; yes, you may push a problem to the staff 09:36:30 chaals: I'd like to be able to avoid having to do that 09:37:43 ... I try to focus on the problematic behaviour; not ignoring the person 09:38:32 ... standing up and saying "look, I'm the authority" will not achieve much 09:39:14 ... without jumping up and down, being clear that a particular piece of work needs to be done, or someone has been standing in the queue, will work with the group most of the time 09:39:50 Zakim, close this item 09:39:50 agendum 10 closed 09:39:51 I see 2 items remaining on the agenda; the next one is 09:39:51 8. action reviews and similar "admin-heavy/traditional" approaches [from chaals] 09:39:53 Zakim, take up item 8 09:39:53 agendum 8. "action reviews and similar "admin-heavy/traditional" approaches" taken up [from chaals] 09:40:21 q+ 09:40:22 chaals: using action review, formally approving minutes, the sort of things, do people do this? 09:40:26 ack ni 09:40:46 Nigel: We do, agenda has a whole part on actions and issues, what's pending, what's due 09:40:50 ... it's important 09:41:05 q+ 09:41:21 ... quite often, I'll put it on the agenda and after prioritising, actions are taken up 09:41:35 ... alternative may be worse: they get forgotten about. 09:41:37 ack an 09:41:54 Andy: We spend a fair bit of time on administative side 09:41:54 q+ 09:42:01 ... sometimes quite useful 09:42:02 s/actions are taken up/agenda items fall off the end and are not covered 09:42:18 ... I'm new to chairing and it's been done that way and it needs to be done that way 09:42:48 ... it's the opportunity to go back on the work people have committed to do 09:43:10 ... admin preamble is an opportunity to beat people up into doing the work, in my experience 09:43:25 ... than, technical work, that is the rest of the agenda, is blocked unless actions are done 09:43:29 s/than/then/ 09:43:29 ack me 09:43:37 chaals: my experience is mixed 09:44:29 ... Because @@ think harder about what they said they'd do, but being more realistic about who can do what 09:45:30 chaals: action item review is useful so long as you're not losing things; action items should not be the whole agenda 09:46:10 chaals: Dan Connolly used to structure the agenda based on action items and actions would crop up under respective agenda items 09:46:29 s/@@/the group 09:47:03 chaals: Out of Andy's point, confirming minutes is a tool I'll remember as a good way to start the meeting 09:47:28 q+ 09:47:35 ack ni 09:48:39 Nigel: I wanted to add that care should be given@@ 09:48:43 s/start the meeting/get people to start the meeting on time/ 09:49:02 s/@@/ to using tracker's agenda tool - it needs to be carefully edited/ 09:49:04 ... also, closing actions gives people a sense the group is making progress, so I try to close as much as possible 09:49:14 chaals: Depends on the WG 09:49:22 ... there are groups that find it very productive 09:49:37 ... there are others which find this is very bureaucratic 09:50:00 ... and for which changing code regularly matters 09:50:07 ... it's a question of degree 09:50:30 s/changing/closing technical questions and changing/ 09:50:56 agenda? 09:50:57 Zakim, close this item 09:50:58 agendum 8 closed 09:50:58 I see 1 item remaining on the agenda: 09:50:58 12. organising meetings [from chaals] 09:51:01 Zakim, take up item 12 09:51:01 agendum 12. "organising meetings" taken up [from chaals] 09:51:09 chaals: Best for last! 09:51:39 ... there has been some serious discussions up and down W3C about organisaing meetings 09:52:13 ... we've had some events in the context of the WebApps WG; strated with a one off meeting, but mostly should have been in the context of WebApps WG 09:52:30 ... on the Process: 09:52:38 ... there are all kinds of ideas of what W3C requires for meetings 09:53:05 ... if you read the Process, there are things you SHOULD do, but nothing you MUST do 09:53:22 ... should have minutes, should be live in IRC so people can follow, should allow remote participation for f2f meetings 09:53:29 ... those are not even mentioned 09:54:44 ... so, I am pushing to get the process changed 09:54:54 ... luckily, I edit the process in the AB 09:55:02 ... the other side is getting the WG to agree to a meeting 09:55:36 ... my bug bear is getting a group that is large to meet outside of Silicon Valley 09:55:52 s/large/large and has members from all over the world/ 09:56:03 ... I don't know if there is anything we can do to encourage people this way 09:56:14 ... any thoughts on meetings, tools? 09:56:25 q+ 09:56:28 ack and 09:56:59 Andy: 50%-50% membership; we try to spread geographically and use TPAC as default 09:57:07 ... generally, membership is amenable to that. 09:57:15 q+ 09:57:22 ack N 09:57:32 s/% member/% US and Europe member/ 09:57:32 Nigel: I'm in the process of organising a F2F 09:57:45 ... looking for a host, and dates, in advance 09:58:00 ... I'm concerned that attendance will be low despite notice 09:58:02 q+ 09:58:04 ... any tips? 09:58:45 ... the other question is paying for food, what do people think about dinner or lunch to discuss outside of context? 09:58:52 ... Should we push this forward? 09:58:55 q+ 09:59:00 q- later 09:59:03 ack an 09:59:12 Andy: we rely on generosity of hosting member 09:59:24 ... if we're lucky they supply coffee and lunch 09:59:37 ... we aim to organise a social evening 09:59:38 zakim, close queue 09:59:38 ok, chaals, the speaker queue is closed 10:00:01 ... inevitably it happens that there's a work/agenda aspect to the social part 10:00:09 -Xiaoqian 10:00:22 chaals: my experience is that people are happy to pay for their own lunch 10:00:26 zakim, call xiaoqian-mobile 10:00:26 ok, xiaoqian; the call is being made 10:00:28 +Xiaoqian 10:00:29 ... people will pay for dinner too 10:00:41 -koalie 10:00:45 ... unless people are sponsoring, I'll go with cheap and 10:01:16 chaals: it's useful to have the people and the place but the rest is administrative details 10:01:27 -LisaSeeman 10:01:41 ... I'll adjourn as we've hit time. Thanks everyone for your input. I will use this to update the wiki as well. 10:01:43 i/chaals: it's/scribenick: nigel/ 10:01:53 -[IPcaller] 10:01:55 -Andy 10:01:55 -gmandyam 10:01:56 thanks chaals! 10:01:57 -chaals 10:01:59 -Xiaoqian 10:02:00 thanks all! 10:02:07 RRSagent, make minutes 10:02:07 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 10:02:09 [Thank you all very much] 10:02:09 -nigel.a 10:02:10 Team_ChTr()4:00AM has ended 10:02:10 Attendees were [IPcaller], chaals, nigel, koalie, yosuke, Xiaoqian, +61.4.097.8.aaaa, Kerry, gmandyam, [IBM-Hursley], Andy, LisaSeeman 10:02:28 [adjourned] 10:02:33 s/resent+ Nigel/resent+ 1-Nigel/ 10:02:48 s/resent+ Lisa/resent+ 1-Lisa/ 10:02:49 RRSagent, make minutes 10:02:49 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 10:03:15 meeting: Chair Training: The Human Dimension 10:03:17 RRSagent, make minutes 10:03:17 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 10:04:19 [end of first session of "Chair Training: The Human Dimension"] 10:04:20 RRSagent, make minutes 10:04:20 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 10:04:54 s/zakim muke me// 10:05:15 s/ mute me// 10:06:19 s/mute li// 10:06:40 s|\me what to do about long time getting people identified in zakim?|| 10:07:36 RRSagent, make minutes 10:07:36 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 10:08:20 s/ 】【‘// 10:08:27 s|s//】【‘/|| 10:08:44 RRSagent, make minutes 10:08:44 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html koalie 10:09:41 koalie has left #chairing 10:13:17 xiaoqian has left #chairing 10:16:14 nigel has left #chairing 16:55:21 RRSAgent has joined #chairing 16:55:21 logging to http://www.w3.org/2014/06/17-chairing-irc 16:55:27 present- chaals 16:55:32 rrsagent, draft minutes 16:55:32 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html chaals 16:56:02 agenda? 16:56:08 zakim, close item 12 16:56:08 agendum 12, organising meetings, closed 16:56:09 I see nothing remaining on the agenda 16:56:24 zakim, this will be chtr3 16:56:24 I do not see a conference matching that name scheduled within the next hour, chaals 16:56:46 agenda+ Introductions (< 1m please) 16:56:52 zakim, clear agenda 16:56:52 agenda cleared 16:57:15 Topic: Second Session 17:04:02 zakim, this will be chtr3 17:04:02 ok, chaals; I see Team_ChTr()2:00PM scheduled to start in 56 minutes 17:04:10 agenda? 17:04:24 agenda+ Introductions 17:29:23 agenda+ Group Dynamics - timing and fatigue 17:30:04 agenda+ More agenda setting 17:52:04 Arnaud has joined #chairing 17:53:46 Team_ChTr()2:00PM has now started 17:53:53 + +1.303.579.aaaa 17:55:54 + +1.617.324.aabb 17:57:28 - +1.617.324.aabb 17:57:50 + +1.617.324.aacc 17:57:57 +TimBL 17:58:34 carybran has joined #chairing 17:58:52 sandro has joined #chairing 17:59:26 +[IPcaller] 17:59:35 zakim, [ip is me 17:59:35 +chaals; got it 17:59:53 MarkS has joined #chairing 17:59:54 deiu has joined #chairing 17:59:55 + +1.831.458.aadd 18:00:02 +Judy 18:00:17 Judy has joined #chairing 18:00:59 zakim, aaaa is Sol-NAB 18:00:59 +Sol-NAB; got it 18:01:03 831 number is Cary Bran w/Plantronics 18:01:19 zakim, aadd is Cary-Plantronics 18:01:19 +Cary-Plantronics; got it 18:01:57 +Jim_Allan 18:02:12 zakim, please mute mit 18:02:12 MIT-32-G524 should now be muted 18:02:23 jim has joined #chairing 18:02:23 zakim, MIT-32-G524 has sandro, deiu, MarkS 18:02:23 +sandro, deiu, MarkS; got it 18:02:48 zakim, aacc is Recording-bot 18:02:48 +Recording-bot; got it 18:03:22 I can scribe. 18:03:34 scribeNick: deiu 18:03:41 scribe: Andrei Sambra 18:04:19 +Arnaud 18:05:03 +AWK 18:05:20 -> https://www.w3.org/wiki/Guide/HumanDimension Wiki page for this topic 18:05:26 +W3C 18:05:54 ddahl has joined #chairing 18:05:56 jeremie has joined #chairing 18:06:02 Zakim, who is on the phone? 18:06:02 On the phone I see Sol-NAB, Recording-bot, MIT-32-G524 (muted), chaals, Cary-Plantronics, Judy, Jim_Allan, Arnaud, AWK, W3C-systeam-office 18:06:04 MIT-32-G524 has sandro, deiu, MarkS 18:06:15 ted has joined #chairing 18:06:15 agenda? 18:06:20 Zakim, W3C-systeam-office has me and ted 18:06:20 +jeremie, ted; got it 18:06:29 Zakim, take up item 1 18:06:29 agendum 1. "Introductions" taken up [from chaals] 18:06:45 +Debbie_Dahl 18:06:50 chaals: I will begin by asking people to introduce themselves for 30 secs 18:07:00 ... what group you're working in, etc. 18:07:10 ... I will start: my name is Charles 18:07:23 ... I am co-chair of the accessibility group 18:07:34 ... let's go with the order Zakim gives me 18:08:03 ack mit 18:08:11 [people introducing themselves] 18:08:39 Sandro_Hawke: staff contact of 8-9 groups 18:08:53 Sandro introduces himself as staff contact 18:08:53 Mark Sadecki: accessibilty staff contact 18:09:04 carybran: I am with Plantronics 18:09:14 Judy: this is Judy with the accessibility team 18:09:38 Jim-Allan: I am the co-chair of the user agent working group 18:09:49 Arnaud: I am Arnaud from IBM, chair of the LDP WG 18:10:03 ... and also to-be chair of the upcoming Social Web WG 18:10:21 AWK: I am Andrew, from Adobe 18:10:33 jeremie: I am Jeremie, the W3C webmaster 18:10:35 s/with the accessibility team/with the accessibility team, and with me is Zhang (Kenny) Kun, based at Beihang in Beijing 18:10:53 ted: I am the head of the systeam at W3C 18:11:15 ddahl: I am Debbie, with the user interaction group 18:11:24 Ted Guild 18:11:27 zakim, close this item 18:11:27 agendum 1 closed 18:11:28 I see 2 items remaining on the agenda; the next one is 18:11:28 2. Group Dynamics - timing and fatigue [from chaals] 18:11:43 Topic: Group Dynamics 18:11:51 Debbie Dahl, Chair of Multimodal Interaction and participating in task force on Cognitive Accessibility 18:12:02 -> https://www.w3.org/wiki/Guide/HumanDimension 18:12:04 chaals: I've changed the page recently, but it doesn't matter if you're familiar with it or not 18:12:33 ... one important item is to make sure the group doesn't stretch too long 18:12:48 ... people loose focus when they are in the meeting for too long 18:12:57 ... so we'll go for 1h and then take a break 18:13:11 ... we have 2 hours and at the top of the hour I will take a break 18:13:41 ... this is something useful for everyone to do (re. breaks) 18:14:21 ... I am hoping to have an interactive session; people will provide their own experience and hopefully have questions 18:14:43 ... do people have experience with groups that run for long periods of time? 18:14:57 ... are groups productive during long sessions? 18:15:04 q? 18:15:04 sandro: I'm used to longer sessions 18:15:29 ... telecons I'm used to are usually 1h, but in crunch times we sometimes go for almost 2h 18:15:47 ... usually we become productive after 45 mins 18:16:11 q+ 18:16:14 ... during f-2-f meetings we usually take 2 hours 18:16:21 ack me 18:17:20 chaals: when people get really heated off and end up with 2-3 people arguing, or 50-80 people people during f-2-f, then is not good to watch just a few people arguing 18:17:31 zakim, next item 18:17:31 agendum 2. "Group Dynamics - timing and fatigue" taken up [from chaals] 18:17:39 zakim, nextitem 18:17:39 I don't understand 'nextitem', chaals 18:17:43 zakim, next item 18:17:43 agendum 2 was just opened, chaals 18:17:49 zakim, close agendum 2 18:17:49 agendum 2, Group Dynamics - timing and fatigue, closed 18:17:50 I see 1 item remaining on the agenda: 18:17:50 3. More agenda setting [from chaals] 18:18:12 chaals: are there any particular items that you would like to discuss? feel free to put them directly into IRC 18:18:19 ... or you can add them to the agenda 18:18:27 agenda+ organising and running meetings (beyond 'process requirements') 18:18:44 agenda: what a chair should do when they have opinions or technical ideas 18:18:49 agenda+ what a chair should do when they have opinions or technical ideas 18:18:52 agenda+ volunteers don't always work to timelines 18:19:15 agenda+ tone, inclusivity... 18:19:39 agenda+ managing conflict 18:19:44 chaals: feel free to keep suggesting things through the rest of the meeting 18:20:02 zakim, take up item 5 18:20:02 agendum 5. "what a chair should do when they have opinions or technical ideas" taken up [from sandro] 18:20:02 ... the topic I am going to take first is sandro's item 18:20:22 chaals: "don't be part of the problem" 18:20:41 ... the specific thing is that most chairs are volunteers and they represent a member in a WG 18:20:53 ... nearly all chairs have extra ideas they want to present 18:21:16 ... what can chairs do to separate their ideas from their chair ones 18:21:25 ... I'm looking for specific problems 18:21:31 q+ to suggest that chairs use the queue when they are talking as members 18:21:36 +q 18:21:49 sandro: so..if it's a little thing, then the chair will pick someone else to run the meeting for a while 18:21:52 q- later 18:22:27 ack arn 18:22:32 ... if there's a proposal made by a chair, then the best solution would be to ask someone else who works for the same organization to propose that item 18:22:59 Arnaud: I am lucky enough to work with people from my company, who represent my interests 18:23:34 ... if you have both hats, you need to specify which hat you're wearing: by default you speak as a chair and they mention when they have a personal opinion 18:23:36 ack me 18:23:36 chaals, you wanted to suggest that chairs use the queue when they are talking as members 18:23:55 AWK has joined #chairing 18:24:02 chaals: when chairs speak as members with ideas, they should place themselves in the queue 18:24:29 ... chairs should not be interrupting everybody; I find it frustrating that chairs sum up what the last person just said 18:24:42 ... I don't think chairs represent those people 18:24:58 ... it's nice if you can avoid the problem by having another chair, but that's not my case 18:25:19 ... in my case I want to be clear about proposing resolutions 18:26:02 ... I try to be very clear about proposals, to make it very distinct when proposing formal resolutions 18:26:14 agenda? 18:26:21 zakim, close item 3 18:26:21 agendum 3, More agenda setting, closed 18:26:22 I see 5 items remaining on the agenda; the next one is 18:26:22 4. organising and running meetings (beyond 'process requirements') [from chaals] 18:26:45 zakim, take up item 8 18:26:45 agendum 8. "managing conflict" taken up [from carybran] 18:26:53 chaals: managing conflict 18:27:01 Topic: managing conflict 18:27:29 carybran: I've been involved with IETF groups re. managing conflicts 18:27:42 ... I'm interested to see how W3C handles them 18:27:53 chaals: there are two kinds of conflicts: 18:28:18 ... 1. people have technical disagreements on issues -- I don't have a magic wand to deal with these issues 18:28:51 ... if you disagree with someone, the first step is to make sure that you can state their opinion in a way they recognize it (so they see you understood their problem) 18:28:52 -> https://www.w3.org/wiki/Guide/HumanDimension#Difficult_individuals Difficult Individuals 18:29:19 ... a coupld of other helpful things: look for data to break deadlocks 18:29:30 ... or how a particular issue impacts the people in the room 18:29:49 s/the people in/the people beyond those in/ 18:30:15 ... there are people who have particular needs 18:30:25 ... those may very well be legitimate needs 18:30:39 ... but there are also people who generate conflicts 18:31:21 ... I'll start with people who "block the work" 18:31:41 agenda+ encouraging participation from group members who don't say too much for cultural, language or personality reasons 18:31:48 shawn has joined #chairing 18:31:54 ... one of the problems is that it is difficult to tell the difference between people who are blocking progress and volunteers who don't have enough time to get things done 18:32:27 ... the most interesting strategy I found is to move the work to a task force 18:32:35 +Shawn 18:32:59 ... if the work happens in a small group where people focus on a specific problem, it becomes harder for people to @@@ negative 18:33:17 -AWK 18:33:20 q+ 18:33:26 ... in a smaller group, there's no one going along with you if you're being negative, so the group can make progress 18:33:27 ack me 18:33:42 ack sand 18:33:47 zakim, mute me 18:33:47 Shawn should now be muted 18:33:54 shawn: this is Shawn, I am W3C staff and co-chair of education outreach 18:34:43 sandro: whenever anybody raises a problem and it seems they might be causing trouble, then you can have them take an action item 18:35:14 q+ 18:35:16 [I am reminded of Connolly's law - those who do the work make the rules] 18:35:19 ack ju 18:35:23 ... if people cause trouble by not getting their work done, then you can "threaten" them to get someone else to help and potentially take over their action item 18:35:32 Judy: I am a bit concerned about that 18:36:10 ... I understand chaals issue, but it almost sounds that if someone is raising an unpopular view, you might be trying to give them an action item 18:36:16 q+ to support allowing others to help 18:36:25 ack me 18:36:25 chaals, you wanted to support allowing others to help 18:36:31 sandro: I can see there is a balance there 18:36:47 chaals: people who are blocking the group are one of the biggest threats 18:37:09 ... the idea of getting someone to help with a person that is not succeeding in their action is surely helpful 18:37:46 +AWK 18:37:51 ... generally I welcome help, but it's not the case with people who are just trying to get you to waste time 18:37:51 s/to give them an action item/to make them take an action item in order to be able to express their perspective; but we need different perspectives/ 18:37:54 ... I'd like to move to other examples 18:38:29 ... there are also people who try to chair from the floor and basically take over the chair's work 18:38:53 ... I personally don't really mind, as I can get to participate as a member of the group 18:38:59 ... my concern is with people who are being ignored 18:39:47 ... some people are less likely to speak up (for whatever reasons) 18:39:56 ... the chair's role is to make sure everyone's voice is head 18:40:05 s/head/heard 18:40:11 q+ 18:40:15 ack sand 18:40:20 ... I find this a challenging part of being a chair 18:40:38 Topic: getting broad input 18:40:39 sandro: my answer is to go around the room and put everybody on the spot, thus allowing people to speak up 18:40:55 q+ 18:40:58 ... it feels awkward to just pick specific people 18:41:01 ack me 18:41:09 ... and it will not work in an 80 person group 18:41:25 chaals: going around an 80 person group and asking everyone to speak up will not work 18:41:41 ... if you ask someone for an opinion, they may not want to give you their opinion 18:41:52 q+ 18:42:19 ack san 18:42:22 ... I tend to ask specific people, but there are also back-channels 18:42:37 sandro: even right now you and I are speaking 90% of the time 18:42:46 q+ 18:42:52 ack dd 18:42:56 ... maybe we can try to do just that right now 18:43:18 ddahl: if you have a small group, it doesn't really address the problem 18:43:33 ... the only way to effectively do that is to do it offline (email?) 18:44:23 agenda+ working outside the group 18:44:31 ... now we have a group of Japanese people who are more comfortable to talk among themselves and they act as a group 18:44:49 q+ 18:44:57 ack me 18:44:57 ... they get a lot more done when they speak in a language they are comfortable with 18:45:10 chaals: how do you handle the dialog with the Japanese? 18:45:37 ddahl: it's almost like dealing with an interpreter -- a slower process that is not ideal 18:45:49 ... we're still getting input that we wouldn't get at all otherwise 18:46:05 chaals: do you manage to have a dialog when an issue arises? 18:46:33 ddahl: we have a person that represents the Japanese group, but it's a non-real time dialog 18:46:51 chaals: standards tend not to happen in real time anyway 18:47:25 ... this relates to another issue: if you take too much of people's time, people will walk away 18:47:54 ... we find people who don't want to listen to people who are not fast and clear in their responses 18:48:11 ... does anyone have experience working with people like that? 18:48:35 ddahl: sometimes the chair has to advocate for people who are taking longer to come up with responses 18:48:59 ... "wait for X or Y to speak up; give them a chance" 18:49:36 chaals: people walk away if others are taking too much time to come up with solutions/responses 18:49:48 agenda? 18:49:51 ... we don't really have a strategy 18:50:03 zakim, close item 8 18:50:03 agendum 8, managing conflict, closed 18:50:04 I see 5 items remaining on the agenda; the next one is 18:50:04 4. organising and running meetings (beyond 'process requirements') [from chaals] 18:50:06 zakim, close item 9 18:50:06 agendum 9, encouraging participation from group members who don't say too much for cultural, language or personality reasons, closed 18:50:09 I see 4 items remaining on the agenda; the next one is 18:50:09 4. organising and running meetings (beyond 'process requirements') [from chaals] 18:50:46 zakim, take up item 6 18:50:46 agendum 6. "volunteers don't always work to timelines" taken up [from chaals] 18:51:12 chaals: this is a different issue, not really a conflict scenario 18:51:34 ... you give people an action item that is supposed to take an X amount of time but it doesn't happen in X 18:51:44 ... I had a recent case like that 18:52:22 ... the obvious solution was to ask someone else to help, which helped a bit 18:52:51 ... but until the two of us sat down and worked together, no work was done 18:53:11 ... are there other strategies people are using to deal with this case? 18:53:33 q+ 18:53:37 ack dd 18:54:11 ddahl: a lot of time people won't respond when nagged about it, and guilt sets in 18:54:25 -Shawn 18:54:29 s/won't/will 18:55:03 chaals: in my case (when it was me) the discussion came up this morning 18:55:09 -> http://www.w3.org/2014/06/17-chairing-minutes.html#item07 this item, from this morning's discussion 18:55:33 ... one idea was to break down tasks into smaller pieces that are easily achievable 18:56:11 [ chaals going over minutes ] 18:56:32 chaals: the other possibility is action item reviews 18:56:57 ... this gives the rest of the group a sense of how much time people spend making progress on actions 18:57:18 q+ 18:57:23 ack san 18:57:23 ... using the review process (not to make people feel bad) to make the group understand how much they depend on someone 18:57:57 sandro: I'm not sure if that example was serious...because the idea of people having 40 action items seems strange 18:58:31 ... the chair would usually avoid giving more action items to a person that cannot handle the load 18:58:33 + +1.503.264.aaee 18:58:44 chaals: I've seen people with long lists of action items 18:59:13 Abramski has joined #chairing 18:59:15 ... I guess it depends if the group is not regularly reviewing actions 18:59:53 Abramski: I am Adam, with the W3C automotive platform group 19:00:19 chaals: I would like to remind people that this call is being recorded and that we should take a break 19:00:31 ... does anyone object to taking 10 mins off? 19:00:55 ... let's adjourn the call for 10 mins; do people want to continue this discussion into the second hour? 19:01:18 ... would you like to do something else instead? we can continue by email 19:01:31 I'd rather continue offline 19:01:31 agenda? 19:01:31 agenda? 19:01:37 I don't have another 1h to dedicate to this but don't let that stop you 19:01:56 offline is fine with me 19:02:02 chaals: 3/4 came up in this morning's discussion (you can take a look at the minutes) 19:02:31 ... I propose to adjourn the meeting 19:02:41 ... please update the wiki 19:03:24 Sol: the question I have (while ok with adjourning) was about my obligation as the AC and AB 19:03:47 s/as the AC and AB/as the AC for NAB/ 19:03:56 chaals: this meeting was about chairs/chairing, but you can write to me and I'll respond with details about your question 19:04:14 -Sol-NAB 19:04:20 chaals: thank you for turning up! 19:04:29 Meeting adjourned! 19:04:29 -AWK 19:04:31 -Judy 19:04:32 -Cary-Plantronics 19:04:32 -Arnaud 19:04:33 - +1.503.264.aaee 19:04:34 -Debbie_Dahl 19:04:36 -MIT-32-G524 19:04:36 -W3C-systeam-office 19:04:37 -Jim_Allan 19:04:37 -chaals 19:04:42 carybran has left #chairing 19:04:50 zakim, aaee was abramski 19:04:50 I don't understand 'aaee was abramski', chaals 19:05:00 zakim, aaee is abramski 19:05:00 sorry, chaals, I do not recognize a party named 'aaee' 19:05:05 rrsagent, draft minutes 19:05:05 I have made the request to generate http://www.w3.org/2014/06/17-chairing-minutes.html chaals 19:05:17 zakim, bye 19:05:17 leaving. As of this point the attendees were +1.303.579.aaaa, +1.617.324.aabb, +1.617.324.aacc, [IPcaller], chaals, +1.831.458.aadd, Judy, Sol-NAB, Cary-Plantronics, Jim_Allan, 19:05:17 Zakim has left #chairing 19:05:20 ... sandro, deiu, MarkS, Recording-bot, Arnaud, AWK, jeremie, ted, Debbie_Dahl, Shawn, +1.503.264.aaee 19:06:07 shawn has left #chairing 19:13:44 jeremie has left #chairing 19:17:49 ddahl has left #chairing