Two Ideas for Future Tech Talks

I keep a notepad with all the tech conference talk ideas I have and jot notes down when inspired. Some talks come together right away, others I work at for years before I actually submit them. A few have been on the list for years with no momentum. I just added two talks that I intended to submit to conferences at some point in the future to my list. Both of these are less technical, but highly important topics.

One of them is about criticism, critique, and feedback that has a working title of “I am an asshole and so can you” that I know I won’t actually use.  I want to explore providing value through criticism, and building people up. I see bad feedback provided all the time (and am guilty of giving it), but I need to figure out what exactly is bad about it.

The other one is kind of meta and is about the UX of conferences.  I want the explore how UX techniques and tools can be used with the various parts of conference organization.  From using personas when deciding on talks and scheduling them to priming and it’s role in introductions. I have a decent amount of thoughts here, but not nearly enough to fill a full slot.

No idea when (if ever) I’ll submit one of these. If you have an opinion on either topic, comment here.  Maybe it will inspire me to actually put real time into the ideas.

2 thoughts on “Two Ideas for Future Tech Talks”

  1. I also have feedback on my list of talk topics to someday/maybe give some day. I remember in a talk I saw in Baltimore last year (which I am not able to find on right now), somebody mentioned that young designers may accept and internalize any and all feedback, and that it’s a process to discover which feedback is worth considering/integrating and which is not. Her point was that there’s feedback from those you trust and are doing good work along with you that is meant to help the work and the person grow, and then there is some feedback which is meant to tear you down.

    Also, this is worth watching, imo:

Leave a Reply

Your email address will not be published. Required fields are marked *