Lessons Learned throughout the day
The lessons-learned were divided into three contexts:
- Personal Context - what did you learn about your own practice
- Activity Context - what did you learn that you could apply or use to help with a specific activity
- Breadth Context - what did you learn that should be applied at the broadest context of the whole organization or enterprise
Personal Context:
- Being intentional and mindful before you go into a meeting. Focus on what you want to accomplish.
- Focus on being able to translate guidance into action.
- Taking a risk, opening up and sharing is part of the architect role. Being willing to be on stage.
- Keep your eyes on the future.
- We have have to define what is best.
- Know not just the result you want but how you will get to the result.
- You need to build influence at the right level in the organization
- Building trust is critical
- Facilitate from the side - guiding and running meetings when you are not in charge
- Look for higher value activities (based on the take Jim gave re: Manufacturing = 1 * Value, Service = 2 * Value, Creating I.P. = 4 * Value, Orchestrating Networks = 8 * Value)
- Need the relationships ++
- Success is possible
- Bring concrete examples to help others understand
- Cannot draw the scope of the Internet of Things (IoT) world - too big, too broad, changing too fast
- Networks are graphs (people connected to other people) - where you touch the network is important (side effects)
- How complicated out work is - actors, technology, organizational
Activity Context:
- Facilitate from the side (that is, help make a meeting successful)
- Use a visual to show how we aren't done - we are still in draft. Popcicle stick house vs. the Taj Mahal.
- Capability map - bring one for feedback
- Outside view will help show value
- having structure helps the conversation (having an activity like building a Strategy on a Page, time limits, etc)
- Educate about the process before you engage to help build trust
- Iteration is important - Start with limited resources then expand to the community.
- Shift and Share is good with a diverse audience. Like the small groups and the choice aspects.
- Use Shift and Share to refresh a stale meeting.
Breadth Context:
- The world is shifting on valuation (see Jim's talk about Valuation). We need to shift too.
- Trust is critical. Need to deliver actionable contributions.
- Scale is important and impactful
- These activities (like building a strategy on a page) can initiate broader conversations
- Shift from "rockstar" developers to collaboration and varied talent
Plus, Delta, Big Ideas and Questions:
Pluses:
- 5-6 people in the groups for strategic planning
- Time boxing strategic planning effort made us write stuff down and not just talk
- Enjoyed being able to contribute on a new topic
- Concrete examples in panel made it real
- Learning how broad the conversation needs to be (especially re: IoT and the Swim Coach story)
- Fresh group of people to work with
- Shift-n-Share, unconference format ++
- As a present, questions and feedback we got
- Emphasis of stories in presentations
- Moving and active after lunch
- No time on artifacts, work is a larger scale
- Framing of the day - EA Holistically
- Notes at the front of the room
- Outside folks in the room (Ann, Steve, Panel)
Deltas:
- How do we get the feedback on strategy, engage the right people?
- Room Acoustics are awful ++
- Agenda on table
- Mix up tables after breaks
- More interaction with peers
Big Ideas:
- The notion of community architecture and sourcing (that is, going into the community and helping them architect their own solutions rather than bringing outside solutions in)
- Switch tables after break.
- Growing architects at home and Higher Education
- Patterns, good transition opportunities
- Keep the conversation going
Questions:
- What is the right balance between producing things (like signature ready artifacts) vs. networking
- What is the role of the architect (in this new world)
Overview
Content Tools