Personal Style - Revision history

ThePlaz: fix links

2013-08-25T06:31:54Z

fix links

ThePlaz: add intro line

2013-08-25T06:31:08Z

add intro line

ThePlaz: add links

2013-08-25T06:29:44Z

add links

ThePlaz: post first version

2013-08-25T06:25:15Z

post first version

Show changes

@@ Line 123: / Line 123: @@
 I don't like to forget something.  I feel that if I don't write it down at the time, I will forget it.  If I feel that I've forgotten something I feel really bad at it and keep trying to remember it.  I kick myself for having forgotten it.
-====To-do lists===
+====To-do lists====
 I'm always making to-do lists.  For example, during my 6 week transition period between MIT and Oracle I have 73 items on my to-do list to take care of between now and then (not including sub-items).  I make checklists all the time.
@@ Line 137: / Line 137: @@
 ===Quantified Self===
-[[Image:File:Fall 2012 Pens.jpg|thumb|Fall 2012 MIT Pens]]
+[[File:Fall 2012 Pens.jpg|thumb|Fall 2012 MIT Pens]]
 I also like to track my productivity; I save all of the pens I use each semester so I can compare.  I think being able to look back and think about your progress allows you to reflect.  It also lets you compare periods - they may feel different, but how different are they actually?
 ==Idealistic Design==

@@ Line 1: / Line 1: @@
-The last few years at MIT has given me many opportunities to reflect on who I am and how I operate.  As I finish MIT, I wanted to reflect back on my personal style.  My personal style is the way I operate; the frameworks I use to guide my decision making and behavior; and my core beliefs.
+The last few years at [[MIT]] has given me many opportunities to reflect on who I am and how I operate.  As I finish MIT, I wanted to reflect back on my personal style.  My personal style is the way I operate; the frameworks I use to guide my decision making and behavior; and my core beliefs.
 In many cases, what I have listed here are the defaults I subconsciously reach for.  With effort, I can do something different, but it is not the default.  Sometimes the norms of a situation calls for different response.  Nevertheless, it's important to be aware of one's biases.  In order to control something, you must first be aware of it.  So by noticing what I default to, I can better adjust to the situation.
-What I have listed here is always evolving. I have noticed some habits change over time, particularly as a result of education. For example, when I was a PM at Disney, I was focused on pushing the project through.  In 14.72 at MIT, I learned that a better model for a PM is to be like a "cocktail host" connecting players together for them to talk, rather than trying to do everything ones self.  At yahoo, the focus is more on getting stuff done.
+What I have listed here is always evolving. I have noticed some habits change over time, particularly as a result of education. For example, when I was a PM at Disney, I was focused on pushing the project through.  In [[14.72]] at MIT, I learned that a better model for a PM is to be like a "cocktail host" connecting players together for them to talk, rather than trying to do everything ones self.  At yahoo, the focus is more on getting stuff done.
 In some senses, I think I am a mix between US and German styles.   I was raised in the US, but my mom is German and I speak German.   Germans pay attention to detail, while people in the US there is also pressure to get stuff done on time.

@@ Line 26: / Line 26: @@
 ====Goal====
 I think this is easier to do if one has a goal in mind - if one is ambitious.  That goal may change, but it's important to feel like you are going after goal.  That goal may not even be well defined, but each person should try to improve their own situation.  Without being able to envision a future for oneself, even subconsciously, it's hard to stay motivated.  I don’t have a specific goal, but I do have a slightly subconscious image of what I want to achieve.
 ===Think Critically/Intellectual Honesty===
@@ Line 81: / Line 80: @@
 ==Platform and Process==
 ===Building a Platform===
-I like to establish my personal "platform."    Jeanne Ross of CISR liked to talk a lot about platforms in [15.571].  A platform gives on a stable platform from which to work.  I like to have all my stuff ready to go.  For example, my computer.  I want a good one that won't lag and get in my way.  I spend the time at the start of the year to get everything set up - so that once classes start, I can be 100% dedicated to that.  I don't want to be distracted by having to fix things.  My platform has to be in place to perform.  For example, I pay $10/month for Exchange email.  I think I'm the only individual to pay for email, but I like something that just works without issue.  In particular, my mail, calendar, and contacts sync between machines perfectly - no problems.
+I like to establish my personal "platform."    Jeanne Ross of CISR liked to talk a lot about platforms in [[15.571]].  A platform gives on a stable platform from which to work.  I like to have all my stuff ready to go.  For example, my computer.  I want a good one that won't lag and get in my way.  I spend the time at the start of the year to get everything set up - so that once classes start, I can be 100% dedicated to that.  I don't want to be distracted by having to fix things.  My platform has to be in place to perform.  For example, I pay $10/month for Exchange email.  I think I'm the only individual to pay for email, but I like something that just works without issue.  In particular, my mail, calendar, and contacts sync between machines perfectly - no problems.
 ===Auto Pilot===
-I try to establish the best ways to do things and then lock onto them as autopilot.  For example, in [Working Out a System], I established over time a way to take notes.  This way I am not reinventing how I take and store notes every day.
+I try to establish the best ways to do things and then lock onto them as autopilot.  For example, in [[Working Out a System]], I established over time a way to take notes.  This way I am not reinventing how I take and store notes every day.
 This is not necessarily static; it changes over time.  For example, I made small adjustments in notes taking over time.  I have some changes listed in an update to Working out a System.  http://wiki.theplaz.com/Working_out_a_System#Changes_Spring_2012 But often I hate to take the time to reset my platform.  For example, I put off as long as possible reinstalling my phone because I knew it would be an hour or two of hassle to set everything back up.
@@ Line 101: / Line 100: @@
 It's important to take history into account.  For example, I think that the classes that have the most history at MIT are the best ones.  This does not mean that they do not change, but specifically that they change ~10% each year.  Changes that are made consider the recent history of what worked and what didn't.
-Too often things exist only because of inertia.  For example, for the [Baker Rooming Review], it was worth taking a look at best practices and then writing up a system.  However, now that the review has been complete, there is no need to conduct a mini-re-review each time the process is run.  By thinking through scenarios ahead of time and writing them down in detail, there is no need to consider each situation from scratch.  However, if it feels like the whole process isn’t working, likely in a few years, it may be better to review it again.
+Too often things exist only because of inertia.  For example, for the [[Baker Rooming Review]], it was worth taking a look at best practices and then writing up a system.  However, now that the review has been complete, there is no need to conduct a mini-re-review each time the process is run.  By thinking through scenarios ahead of time and writing them down in detail, there is no need to consider each situation from scratch.  However, if it feels like the whole process isn’t working, likely in a few years, it may be better to review it again.
 Having a process means stuff is less ambiguous.  When setting up a process, it's important to think through all of the corner cases.  This is just computer code.  When it place, it should make decisions easier.
@@ Line 136: / Line 135: @@
 ===Quantified Self===
 I also like to track my productivity; I save all of the pens I use each semester so I can compare.  I think being able to look back and think about your progress allows you to reflect.  It also lets you compare periods - they may feel different, but how different are they actually?
@@ Line 153: / Line 152: @@
 I like when things are well-specified.  For example, at MIT, the dining plan as of 2013, is billed as all-you-can-eat.  However, for some premium items (ie. scallops) the dining contractor wanted to limit portion sizes because they were only able to order limited quantities with their budget.  I think it's good that we can have premium items at dinner.  I recognize that because such items are rare, they will be highly demanded, so the items can only be offered at limited quantities.  I have no problem establishing a limit for those items.  In fact, I had even originally proposed a hybrid limited entrée, unlimited sides program when the program was being hashed out.  However, I think the plan should be carefully thought through with all stakeholders, instead of coming up with some way to limit items on-the-fly.
-This is because I think it's best to think about a solution up front - in a process when you have time to read the latest research, explore options, consult stakeholders, and then arrive at a robust policy.  I'm a big believer in the stakeholder consultation process - as I described in my [white paper].  Then when it's time to implement the plan, you just have to do it.
+This is because I think it's best to think about a solution up front - in a process when you have time to read the latest research, explore options, consult stakeholders, and then arrive at a robust policy.  I'm a big believer in the stakeholder consultation process - as I described in my [[:File:Unrelenting Advocacy.pdf|white paper]].  Then when it's time to implement the plan, you just have to do it.
 Emergencies are like this as well.  What if there is a intruder in Baker House? How should the desk person react?  Instead of wasting time considering actions, or taking the wrong action (evacuating the building instead of sheltering in place, for example).  When I was at Disney, I visited Disneyland's Emergency Operations Center.  They had a thick binder of every possible thing that could go wrong (power line out, flood - even though it appears to me that Disneyland is not really in flood danger, etc).  For all of their attractions, they have hundreds of pages of documentation.  They spent time figuring out how to do it right, and now each person doesn't have to start from scratch.
@@ Line 190: / Line 189: @@
 I'm made a pattern out of knowing the people at the top and bringing well-formulated concerns or insights to them, especially about systemic issues.  I think many people  just think the higher up is uninterested in what they have to say.  However, the higher up's job is the systemic design!  Thus, they are often very interested in your insights on systemic issues!
-It's important that insights be well formulated.  Many issues are local; it's only once the local structure fails repeatedly that the issues becomes systemic.  For example, I had some trouble with the SAO office at one point at MIT.  In my letter to Chancellor Grimson, I didn't speak about my problems, except as examples of systemic issues.  I tried to include comments from other people which corroborated my examples.  I also tried to limit to comments to things which were objectively wrong.  For example, in my [ [14.02 Complaint Letter ]] I limited my comments to logistics because those where the ones I feel like I could support.  (Reviewing that letter two years later is kinda embarrassing, I think my letter writing skills have improved since then)
+It's important that insights be well formulated.  Many issues are local; it's only once the local structure fails repeatedly that the issues becomes systemic.  For example, I had some trouble with the SAO office at one point at MIT.  In my letter to Chancellor Grimson, I didn't speak about my problems, except as examples of systemic issues.  I tried to include comments from other people which corroborated my examples.  I also tried to limit to comments to things which were objectively wrong.  For example, in my [[14.02 Complaint Letter]] I limited my comments to logistics because those where the ones I feel like I could support.  (Reviewing that letter two years later is kinda embarrassing, I think my letter writing skills have improved since then)
 Writing good letters helps build up one's reputation.  As one sends good letters, one's reputation increases, earning the trust of the person, that you are emailing them about important systemic issues.  This pays dividends.   So you need to be brave and send.
@@ Line 206: / Line 205: @@
 I like to think about organization design.  Organization design is really interesting.  I'm interested in what are the most efficient ways to do something.  I really liked these types of classes at Sloan, and to read Harvard Business Review.
-At MIT, I wrote white papers about [A Framework for Community Engagement] and [Problem Solving Teams] suggestions to improve MIT.  I like to set up new systems.  It's just fun to think through all the complexity and come up with the ideal system design.
+At MIT, I wrote white papers about [[A Framework for Community Engagement]] and [[Problem Solving Teams]] suggestions to improve MIT.  I like to set up new systems.  It's just fun to think through all the complexity and come up with the ideal system design.
 I like to work in, what I call, "close-in teams."  Most importantly this means the team is one place.  Working with remote teams is a real drag.  In person, you can see when your boss is around and not really busy.  I don't like calling because I don't know if someone is busy or not.   So then you are limited to pre-planned meetings which have at least 1-2 days lead time.  It also means that team members know each other real well and are comfortable working together.  It also means trying to limit external dependencies.