[-- Note inserted by JeffT (Administrator) --
This thread is for discussion by non-candidates about some of the issues raised in the elections Q&A threads. By popular demand, we are splitting off the threads and creating a place to discuss them. That way the Q&A threads can be focused for those following the elections.
Apologies for editing Michael's post--it's the only way to insert this notice at the top of the thread.
-- End of administrator note --](edit, copied my last post with this...)
What do you see as the greatest logistical challenges to spreading ourselves over 2 non-neighboring hotels?
How do you envision addressing them?
Logistically the hardest problem will be convincing our attendees to split up between the two venues without literally strong-arming them in to it.
From memory of three years ago and the websites I'd say that we should /very/ strongly look in to setting up a point to point wifi relay using directional antenna and openwrt/ddwrt flashed routers between the two hotels and use that to carry a live CCTV feed of the other stage. If possible any video presentations should be displayed locally at each site.
Since there are two rooms setup, one should be used as a dance/rave setting. The other could have an alternative dance or concert; which addresses a complaint from R&R this year.
Looking at the room layout I'd suggest allocating rooms towards panels in such a way that people naturally want to divide between the two locations to some approximately even degree. However that also depends on Programming scheduling use of those rooms in that 'evil director' diabolical way that encourages prioritization of event viewing to drive that decision.
What do you think was done well in Operations this year, and what do you think we need to keep doing (or reinforce) to make sure it stays that way?
Unfortunately I don't know what did go well in Operations this year: I think from our attendee point of view the convention was a spectacular success. So most of what operations did was excellent.
What do you think could have been done better in Operations this year, and what specific changes would you implement to make it so?
Most of the failings Operations did have this year fall in to three categories:
More Yojimbo were needed. From the sound of things this was an extremely last moment change too. HOWEVER the way we take on Yojimbo and already expect them to work as if it's the worst-case scenario both reduces the likelihood of them joining AND means that if something does hit the fan at the last moment there's no slack within the department to handle it.
If there were soft deadlines and final hard deadlines for things a few of them were missed. When such things are hit normally extra resources are assigned to work in parallel from another angle. There are also some things that cannot afford to fail from the beginning and must go to the last moment. As Jeff is fond of calling it, a 'no power' plan for working through registration.
I'm not sure of where this got dropped, but since I hadn't received any prior notice before arriving at the convention I had no /idea/ I'd suddenly go from working 100+ hours before the convention to also working 16 at it. In my choice of shifts from 06:00-14:00, 14:00-22:00, and 22:00-06:00 no less; two of which more or less split when I usually crash at conventions. However assigning shifts in 2, 3 or at most 4 hour blocks was addressed in R&R. I'd also say that for any 'fixed' area position only a 2 hour shift should be assigned. A 4 hour should only be assigned to shifts that involve roaming around an area and which allow for taking a brief restroom break during.
How will we be able to recognize that you're doing your job when you give progress updates, and if you don't meet this standard will you be willing to step down?
Soft deadlines. They don't all have to be met, those are the warnings that things aren't going to plan. If I'm the problem, or fail to meet a hard deadline, I'd readily offer my head to the board and through them to the convention.
Assuming they would accept, who would you choose to fill the key Operations manager positions? (If you don't know of anyone whose qualifications make them a prima facie choice for any given position and want to choose through interviews, just saying "Interview" is fine.)
My first choice would be asking former directors and those who'd filled the position in prior years who they recommend for the job. There's also the slightly more fair and slightly less expedient method of asking the staff who they thought was on the ball in their department.
I really only have one question for the candidates: Will I be allowed to work in the Con Suite again?
I don't know of anyone who was a problem so I don't think I'd disallow any staff from doing so.
What tasks were you assigned in your position this year, and how did you perform on those?
I nearly started one of my tasks too late because I hadn't thought to ask for a soft deadline on it and nearly got bitten when a quite unexpected hard deadline was delivered. I feel that I did complete things quite well once I was given a deadline, and that's one of the things that I learned from being staff this year. /every/ task should have a soft deadline, followed by maybe more, and then a final hard deadline.
Specifically tasks that you hadn't planned to deal with as part of your job.
Manning the elevators. I think given the situation I was reacting well, but I honestly got too stressed out by elevators arriving in huge bursts or not at all, and the general confusion spreading in to the attendees. Next year I would very much suggest designated line up and route in/out areas for elevators; via tape on the floor if we can, or poles and rope if not. I'd also suggest marking off every quarter elevator section in the line-up area so that it can be directed by car portion. (However don't tell the attendees that. Just number it sections 1 to 8.)
What other time sinks do you have outside of con? It is imperative that the Operations Director be available to the con for it's mini-events like dances and outreach events. Also being able to make reg meetings, board meetings, and general meetings is priority #1.
This is an extremely good question that I hadn't considered. I knew of the board meetings, and could schedule time to attend those as well; BUT attending everything else was /not/ in my plans at all. This is actually the first question that would have made me reconsider on my own.
Do you plan on attempting to put together team building events mid-year for your staff? Having the Yojimbo get together more during the year would be something the crew would really appreciate I think.
I think picnic/game day style things worked really well this last year. We should do those at least once a quarter, and encourage a few hours of game play at the event for mingling and using names. Large name tags should be required. (If I say your name 15 times there's actually a chance I'll remember it...)
How do you think you'll go about getting the software guys to be able to set up a system like this?
Oops, I cut off a bit of the question, but I remember it. Yeah, during the 2 hours that I did check-in I was extremely surprised lookup by that key wasn't there. Even just /sorting/ the print output for the 'have badge, checking in now' station by that key would have vastly sped up my lookups. It would be utterly /trivial/ to build a website in at least PHP, and probably any other language that had a database driver to talk to a copy of the DB and load up a template badge for visual confirmation as well as track parent permission forms and other items. Plus this data would be static on site and be more secure without Internet access anyway.
How do you plan to get computers with the software on them for con?
I think the idea that was tried in 2007 would work well here. Anything at all that can run a live CD talking over a secured, HARDLINE, network to a laptop running the DB and web-server sounds good. Any old thing would do really, a few hundred megs of ram and an OK disk could keep up with that client load.
Also, dress-rehearsal is un-necessary; unless you mean beta and usage testing to make sure that the software fulfills the client's requirements.