Architekwiki
  • Home
  • WIKI
  • Start Here
  • Resources
  • Other
    • Reading List
    • Ochre >
      • Ochre
      • Ochre KB
      • Ochre FAQs
      • Ochre Help
    • Details
    • The 3 Aspects
    • About
    • Subscription FAQs
    • Terms of Use
  • Subscribe
  • Home
  • WIKI
  • Start Here
  • Resources
  • Other
    • Reading List
    • Ochre >
      • Ochre
      • Ochre KB
      • Ochre FAQs
      • Ochre Help
    • Details
    • The 3 Aspects
    • About
    • Subscription FAQs
    • Terms of Use
  • Subscribe

Architekwiki

A Resource For Architects
Click here to get good stuff in your inbox

Categories

All
Business Development
Business Management
Design
Detail
Miscellaneous
Project Management
Resources

Archives

January 2023
November 2022
October 2022
July 2022
June 2022
May 2022
April 2022
October 2021
September 2021
August 2021
June 2021
May 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012

Lessons Learned

9/5/2016

 
Lessons Learned
One of the major differences I found between designing projects in school and designing projects in a firm was the need to meet others' expectations. To me school design was like solving a puzzle. Having a solution was what mattered. Not how you got there.

​When I was designing 'for real', I was never entirely on my own like in school. Getting all the drawing done in time for final printing was just one objective. The client needed to be kept in the loop. The consulting engineers needed drawing updates in time to complete their work. And they needed them far enough in advance for me to make sure their work was coordinated with everything else. Codes. Budgets. Specs. Having all these other expectations encouraged me to find a process. 

That's where Lessons Learned comes in.

Lessons Learned
Eventually I stumbled across the use of checklists so that nothing was overlooked. Then the checklists got smarter. Tasks or part of tasks were moved around so they would be done at the 'right time'. Partly because I was sick of consultants bitching, "I wish you had told me that a lot sooner." Partly because I could see I was making extra work for myself as well.

One of my flaws or advantages is that I can see how to improve things without really trying. It just happens. It is maddening to be on deadline and find yourself planning how to save time and effort "next time". That's the stuff of all-nighters. On the other hand when 'next time' comes around, I have a better plan. ​

I have to admit that I can't remember all the ideas that I get for improving things. So Lessons Learned is a way of filing those ideas and experiences away for next time in a way that will be easy to implement - next time.
​

There could be an even more effective way of keeping your ideas and experiences handy, but this is what worked for us. There was quite literally a 'Lessons Learned' file for each client and consultant. More about that below.

​The main technique for capturing Lessons Learned was to embed the information in our filing system. Here's how that looked. (See screenshot on right.)

​The "0 Master Project Folder Template" was the starting point for each new project. The zero in the name assured its first place in the list of projects - easy to find. You simply copied the folder and renamed it for each new project. This gave you not only the latest thinking on how information should be filed, but also all the latest templates, checklists, and Unique Methods 'flow charts' to use on the project.
Lessons Learned
For instance "AgendaMinutesNotes" contained a formatted template for use in making your first agenda. This template contained our knowledge about Agendas in the form of a checklist. Copy it. Rename it by adding the date in YYYYMMDD after the "Agenda" title. And you were ready to go. The point is that you didn't have to look for this information. It was right where you needed it.

​It was just as easy to make an improvement. Just modify the master document in the master project file folder. This method for embedding our knowledge covered all aspects of project work. 

The same approach was used for Business Development and Admin/Finance so that, whatever you were working on, the firm's knowledge about that topic was right there in the folder you were using.
Lessons Learned
​Unique Methods is a fundamental improvement concept. Here are posts on Unique Methods.

Do You Have Unique Methods?​

Unique Methods Revisited
​

Building Value With Unique Methods
​
Lessons Learned
Not everything is categorized into those main folders. Like CAD. CAD Standards were contained in a subfolder right at the top of the PROJECTS folder for convenience. As I mentioned above, each client had a Lessons Learned document. Once we had two projects for the same client, all their projects were filed together as sub-folders to the client's name. The Lessons Learned doc was moved to that level for easy reference and high visibility when working on any of their projects. This post gives an example of a Lessons Learned doc. 

To some degree everyone does this kind of thing. In order for it to build up to something worthwhile, it has to be easy to retrieve. Even better is having it be noticeable frequently in the normal course of events.
​
Do you have a solution for capturing your knowledge and experience to share?
​

​Aside to Wolnitzek Architects alums who see this:
Yes, I know that this isn't exactly the system that we had. 
But it should have been.
Lessons Learned
If you would like articles like this sent to your inbox, SUBSCRIBE.

Create your competitive edge. Trello-PM. A Project Management guide.

Use FeeCalqs, a digital Fee Calculation tool.

​
​###

Comments are closed.
    Resources

    Start Here

    YouTube Channel

    Join The Mailing List

    Terms of Use
    Your use of Architekwiki is implicit agreement with the 
    ​
    Terms of Use.
    Thank You for your donation

    x
    Get Good Stuff in Your Inbox
    Picture
    Subscribe

    RSS Feed


    Archives

    January 2023
    November 2022
    October 2022
    July 2022
    June 2022
    May 2022
    April 2022
    October 2021
    September 2021
    August 2021
    June 2021
    May 2021
    February 2021
    January 2021
    December 2020
    November 2020
    October 2020
    September 2020
    August 2020
    July 2020
    June 2020
    April 2020
    March 2020
    February 2020
    January 2020
    December 2019
    November 2019
    October 2019
    September 2019
    August 2019
    July 2019
    June 2019
    May 2019
    April 2019
    March 2019
    February 2019
    January 2019
    December 2018
    November 2018
    October 2018
    September 2018
    August 2018
    July 2018
    June 2018
    May 2018
    April 2018
    March 2018
    February 2018
    January 2018
    December 2017
    November 2017
    October 2017
    September 2017
    August 2017
    July 2017
    June 2017
    May 2017
    April 2017
    March 2017
    February 2017
    January 2017
    December 2016
    November 2016
    October 2016
    September 2016
    August 2016
    July 2016
    June 2016
    May 2016
    April 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    October 2015
    September 2015
    August 2015
    July 2015
    June 2015
    May 2015
    April 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014
    February 2014
    January 2014
    December 2013
    November 2013
    October 2013
    September 2013
    August 2013
    July 2013
    June 2013
    May 2013
    April 2013
    March 2013
    February 2013
    January 2013
    December 2012
    November 2012
    October 2012

    Categories

    All
    Business Development
    Business Management
    Design
    Detail
    Miscellaneous
    Project Management
    Resources

Picture

Picture
VISIT ARCHITEKWIKI'S RESOURCES
​
START HERE
ABOUT
SIGN UP
TERMS OF USE
Architekwiki | Architect's Resource | Greater Cincinnati 
© 2012-2022   Architekwiki​