I am Jon Morgan | December 2011

Published on May 2016 | Categories: Types, Creative Writing, Essays | Downloads: 36 | Comments: 0 | Views: 177
of 20
Download PDF   Embed   Report

I am publishing the first ebook version of my blog "I am Jon Morgan." I plan on releasing ebooks in the future.

Comments

Content

1/20

I am Jon Morgan December 2011

2/20

Table of Contents Technology Don't Be Like Marney On the Web, what goes up must come down (Eventually) Do you know where your content is? What is Storybag? What is Project Hover? Lifestyle A Memorable Weekend Enjoying the Great Weather on Friday

3/20

Technology

4/20

Don't Be Like Marney
I came across a letter on Awkward Photos that made the rounds a few years ago as an email forward. It’s written by someone who is hosting a holiday dinner (I think its Thanksgiving) and communicating with the attendees about what they need to bring. The letter kind of goes off the tracks when “Marney” begins to assign dishes to specific members of the family and describes exactly how the food should be prepared, down to the ingredients and even the way that they are served. You can read the scanned version of the letter here. After reading the letter, I started to think a little more about what was going on behind the scenes, inside Marney’s head, and inside the heads of the other family members who would have recieved this (supposedly real) letter. Marney, apparently, has a vision for how she wants her dinner to go and how the food should taste. She knows that even though she is able to make every dish she’d like to serve during dinner, its just not practical for her to do so. Maybe she’s limited on time, or it would be too expensive. So, she is enlisting the help of her relatives. But, this is where she has gotten things a little wrong. She is letting go of the process of preparing food, but she has not given up ownership of the food. She is adhering too closely to her original vision for what she wants the dinner to be. It’s her “show.” If she understood human behavior, or at least the personalities of her relatives, she would understand that dinner needs to be a collaborative process. Sure, Marney should be the one to decide how many pies they will need or maybe even who should make the stuffing, but the rest should be left up to the person doing the cooking. There is some risk in doing this because you are actually blending different cooking styles and skills together, and you might end up with some suprising results. But, everyone benefits because they are contributing equally, and Marney is able to focus on her other duties as a host. What Marney needs to do is to recognize that as the host she will have control over the key aspects of her party, but not over everything. If instead of telling someone “This is what you need to bring, and how you need to prepare it,” she said, “You make the best pies. Would you mind baking two?” things would go a lot more smoothly. Companies are sometimes lead by managers who carry around such a locked vision in their head that they are not willing to allow others to fully contribute. They micro manage the details so precisely that they start to sound like Marney in the letter about dinner. This is what will happen, and here is how it should look or act. Then, much like Marney, they might wonder why they didn’t get the results that they were hoping for. Websites are the trickiest to micro manage because, much like a Thanksgiving feast, web projects are dependent on so many different disciplines and types of expertise. It is also interpretive and subject to change based on what works, what doesn’t, or what users need. The best thing for a Marney-like manager to do is to sit back and ask themselves, “What is my objective?” If their objective is to produce a website exactly the way that they envisioned it, then their next step should be to careful defined exactly what they want, how they are going to do user or market testing, and what roles other project members will play in the proces of

5/20

development. But, they might find that it will be a struggle to maintain their vision with so other competing factors such as usability, limitations, etc. A better approach would be to define what you want the website to accomplish. Typically this might be to change lives, make a task more convenient, etc. When you focus on an objective like this, you will find that the project will be easier to manage. When team members are allowed to contribute equally, the results are much sweeter. Marney seemed to forget, for example, that the purpose of bringing everybody together for Thanksgiving was to be able to see family. Once everyone is talking and enjoying each other company, they won’t really care about how the food was presented. When relatives prepared food for Marney, they were doing it for three reasons: to help her out, out of a love for cooking, or because they looked forward to spending time with family. Things were guaranteed to go badly when she made the meal all about her. I experienced my own, Marney-like feelings when I worked on a student-run comedy skit show in college called “Aardvark.” Although I ended up operating cameras and acting, my original goal was to write scripts for the skits. Wrote the scripts with pride, carefully describing what I wanted the actors to do or say. I would bring copies of my scripts to a taping, distribute them to the cast, and then watched with dissappointment as they adlibbed lines or didn’t follow the directions I had included on the pages. I felt very protective of my work at first. I could have stepped in and pointed out their mistakes. But, as I thought about it I realized that my skits were actually getting better when the actors were able to add in their own interpretations. The shows were very much a collaborative effort, and while my ideas and scripts were an important part they were best used as a starting point. Looking back at my situation with my non-Marney point of view, I see that it really helped me to remember that everybody had come together to produce a comedy skit show, not to read Jon’s scripts verbatium and do everything that he said. If you want to see the consequences of not allowing collaboration in your project, just look at the comments which follow the letter from Marney. These aren’t relatives, but they sympathize with anybody who would have recieved the letter. Some say that they have relatives who actually behave or sound like Marney. When it comes to dinner or projects, nobody likes to be micromanaged. And, I’m arguing that there is a middle ground where managers can allow their visions to evolve without giving them up completely. During the production of “Aardvark,” everybody’s acting stayed true to the spirit of my scripts even if they didn’t follow every letter. Given enough direction and space, a project team can take their assignment and run with it. So, my message today is Don’t be like Marney. Define what you need from your web project ahead of time, and then approach your web team with questions. Leave room in your vision for the team’s ideas. Be your customer’s advocate, not purely your own. Stay focussed on the objectives. Think of your company’s business objectives as the main course, and collaboration with your team as the dessert. And, during any meal its important to leave room for dessert.

6/20

View as a Blog Post:

http://iamjonmorgan.wordpress.com/2011/11/25/dont-be-like-marney/#more-92
Edit or Comment:

http://iamjonalanmorgan.wikispaces.com/Don%27t+Be+Like+Marney

7/20

On the Web, what goes up must come down (Eventually)
In the world of web design, we’re always putting stuff up. We ask, “Is that article up?” or “Did you upload that photo?” or “Did you post up that blog?” We are so focussed on getting everything up, up, up onto the web, that I think its too easy to sometimes remember that the stuff we share via a website needs to eventually come back down. This doesn’t mean we need to remove the stuff, but maybe it should go away or get replaced after a while. This would help keep content looking fresh on a website. There are some kinds of content that just cries to be taken down. Like, when we put a holiday greeting and suddenly its January. We take it down. But other types of information aren’t quite so obvious. Like, a description about a service or a letter to readers. Sometimes we think that its more efficient to leave a letter to readers or description of a service up online than to be always changing it. There are, after all, a steady stream of people who haven’t read seen them before. When we launch astronauts into space, either as the crew of a space shuttle or the International Space Station, I’m pretty sure that we always have a plan for bringing them back down to Earth. I’ll also guess that it is (or was) common practice for NASA to stay in constant contact with the crew during a mission. We should treat our content in the same way. When it goes up, we should have a plan for taking it back down, or changing it at the very least. While its up, we should check in on it to see how its doing. This might mean sprucing up parts that might be growing stale, or looking at stats. Sudden irrelevance might cause us to “scrub the mission,” and bring the content down again. Hight traffic could mean leaving it up longer. Maybe even irrelevance is irrelevant, as long as visitors are finding value in the content. So, when you’re launching a new page for your website, or writing a post for your blog, ask yourself how you will manage the content, and when/how you are gonig to take it down.
View as a Blog Post:

http://iamjonmorgan.wordpress.com/2011/11/23/on-the-web-what-goes-up-must-come-downeventually/ Edit or Comment: http://iamjonalanmorgan.wikispaces.com/Don%27t+Be+Like+Marney

8/20

Do you know where your content is?
A year ago, I began working with my sister-in-law Susan who had started a page on Facebook for her flower shop, and needed to move her business website to a different hosting platform. I had recommended starting a blog using WordPress’ free service. As I worked with her, I discovered that the hardest part to getting her up to speed in social media was helping her to manage all of her online assets. This included catalog entries, posted updates, and business transactions. At first, I tried using Fogbugz but it really didn’t handle things the way we needed for social media, plus it was too technical for Susan to work in. At the same time, I was struggling with the same kinds of questions else where. At work, where EduGuide was slowly ramping up a social media presence, and also at home where I was working out ways to distribute content across the Internet. Things used to be easier back before the Internet because content could only come in one of two different forms: draft or published. If it was a draft, it was still “in-house,” and then of course when it was published, it had been published inside a newspaper or some other type of publication. The review process for content has change drastically since the Internet’s growth in popularity, as well as the rise of the social media networks. It has become apparent to me that it is important these days to publish as quickly as you can. The “review process” is now handled publicly via crowdsourcing. Changes are made on the fly, either to the original content, or as comments, updates, etc. The challenge of this new methodology is that it is much harder to track your content when it has been shared or published in ten or twenty different places at the same time. Back before newspapers were digital, for example, editors probably weren’t always aware when Aunt Matilda clipped out one of their publications’ articles and mailed it to her son. But, today when this is done the article is usually sent as a link. Not only is this trackable, but in the age of social media it very much matters to editors how their content gets shared. I’ve discovered that content is easier to track if you begin tracking it from the very beginning: at some point during the editorial process. You write an article and–boom, a record is started where you can track the article throughout its lifespan. If you start a discussion–boom, record it in the same database. Posted a photo? Same thing. Correct me if I’m wrong, but there doesn’t seem to be a system which allows you to do this. Sure, there are social media management services, or you could record this activity in a database or spreadsheet, but even these tools wouldn’t be able to cover all of the angles which come with social media. So, I built one. My target publication is my blog at http://iamjonmorgan.wordpress.com. My assets are the blog posts I publish there. Most of my writing is done in Posterous and simul-casted to http:// iamjonmorgan.posterous.com and http://iamjonmorgan.tumblr.com, but I’ll explain why during a

9/20

later blog post. And, for the purposes of this description I will focus on my WordPress blog. When I write a blog post like the one that you’re reading, I’ll want to track comments and page views. But, the same blog post will also be shared via Facebook and Twitter (thanks to Posterous’ autopost feature) and could potentially be shared via other networks like LinkedIn or Google+. I originally planned to track my online assets inside FogBugz, but I found that it was a bit cumbersome and that when I flowed in every email I recieved from every profile it was overwhelming. I recently started to use a service called Tender to collect these same kinds of email messages. I can review items, delete them, add notes, or send them on to the next level of review. Lighthouse is a tool which acts and looks a lot like Basecamp but allows you to manage tickets in a way that’s similar to FogBugz. It is also made by the same company which developed Tender, so the two tools integrate really well. My plan is to delete the items in Tender that aren’t useable and attach the items to a Lighthouse ticket when I think that they can be used in my blog or social network. I can associate more than one submission in Tender to a ticket in Lighthouse, so if I see a lot of posts which are related to the same topic of, say, “Thanksgiving,” I can associate them all to the same ticket. Right now I’m the only one managing tickets in Lighthouse, but I plan to eventually include more people. Tickets can be responded to via comments, modified, tagged, and re-assigned to other members of the project. I plan on referring items to editors for review, authors for revisions, and project members in other roles when the need arises. A key advantage of this system that an item doesn’t have to go all of the way through this process before its pushed out to the web. If there is an upcoming event, for example, then anybody who wants to post it on their Facebook profile or on one of the Facebook fan pages is welcomed to do so. We would just want to make a note of it in Lighthouse so the post can be tracked. But, for the most part an item would have been published on the Internet before being recorded in Lighthouse. Once an item is “approved,” it would be assigned to my Project Hover FogBugz account. This would allow us to close the item in Lighthouse, but use FogBugz to continue tracking its progress. Updates in Lighthouse would be noted–even if not posted–in FogBugz. If an item leaves Lighthouse it has been published on the web and revised. I’m keeping it inside a flow because now I want it to be a part of some kind of compilation. This serves my own pruposes, but perhaps this could be used to follow up on a news story, respond to reader’s comments, or perhaps turn readers’ comments into a brand-new story of some kind. FogBugz still isn’t suited for tracking content, but it is still a good tool for recording activity or other types of information. It can also be integrated with a project management tool which I discovered recently called Pivotal Tracker. Pivotal Tracker displayes your list of projects in two to three columns. You have “Current,” “Backlog,” and “Icebox.” When you integrate it with FogBugz, you will also be able to open up a column where you can import FogBugz tickets. Once imported, your notes in Pivotal Tracker are saved in FogBugz, and when you update a ticket in FogBugz, its associated entry (or story) in Pivotal Tracker is updated. My plan is to use Pivotal Tracker to track the remaining lifespan of a piece of content. Items can

10/20

be watched or arranged together based on how you want to use them next. They can also be categorized using tags. For example, this blog post may start out in WordPress, but eventually it will appear in Pivotal Tracker as an item in a list. When I’m ready to compile posts together in a book, I will go through the list and group together the ones that I like the most. As I add them to the book I’m publishing, I will mark them as “done” in Pivotal Tracker. Their ticket in FogBugz will also be marked as “resolved.” The tracking continues after the content is included in an ebook because there are still opportunities for readers to respond with comments or questions. I can continue to track this activity using Pivotal Tracker and/or FogBugz. In the end, when I include web metrics with that kind of activity, I will get both a history and a very strong idea about my content’s effectiveness. I will be using this technique for Social Media Management for both Project Hover, and Storybag. You can view the different parts of this system here: ● http://projecthover.tenderapp.com - Project Hover Tender ● http://projecthover.lighthouseapp.com - Project Hover Lighthouse (project) ● http://projecthover.fogbugz.com – Project Hover FogBugz ● http://www.pivotaltracker.com - Project Hover on Pivotal Tracker Most of these are free to me to use right now, although I am going to need to approach Tender about seeing if I can use their web application for free under their startup discount. I’m not a startup, but I feel like I am starting something. Hopefully that argument will be convincing enough when I talk to them. The lighthouse and pivotal tracker projects are public, so you shouldn’t need to create accounts before viewing the information there. You will need to create an account before joining either of these projects. I’m going to ask everyone who is involved with Project Hover to join the Lighthouse project; this is where our team would collaborate the most. Book editors would also focus on items in Pivotal Tracker, and community managers (fan page administrators, etc.) would probably also be responsible for monitoring discussions in Tender. Although I’m not using Tender the way it was intended, I do hope that it could serve as a forum where authors, editors, and readers can discuss ideas for future blog posts, ebooks, etc. If you have any concerns or questions about how this would work, please feel free to email me at [email protected] or contact me via twitter at @jnmrgn. You can also respond directly to this blog post and find other contact information on my blog at http:// iamjonmorgan.wordpress.com.
View as a Blog Post:

http://iamjonmorgan.wordpress.com/2011/11/23/do-you-know-where-your-content-is-thelogistics-of-managing-content-in-a-social-media-world/ Edit or comment: http://iamjonalanmorgan.wikispaces.com/Do+you+know+where+your+Content+is%3F

11/20

12/20

What is Storybag?
While I worked for Dow Chemical’s Video Conference Help desk, I had a co-worker who I would sometimes talk to named Steve. One day, we got onto the subject of social media sites like Facebook or MySpace. Steve said that these sites were a waste of time because there wasn’t any value to the information being posted. It was all information for the sake of sharing information without a defined purpose. I’ve thought a lot about that conversation over the year. I’ve seen a lot of great things shared over Facebook and Twitter, but I often wondered if there was some way to add a little more purpose or meaning to social media. The “Experience Project” comes the closet to being social media with a purpose. The whole site is geared towards collecting member’s recollections of their life experiences. And, I’ll admit that there are a lot of blogs that are written to serve a clearly defined purpose. My search brought me down a path with key objectives. Define a purpose, recruit people, collect content through crowdsourcing, and then publish the results across different media. So, it would be a project that was as clearly defined as the Experience Project, but broadly focussed like Posterous. It would also need to be a community without borders, because I would want to accept submissions from any of the popular networks. And, since there were no borders, I would need to be careful about the way in which the content is collected, and then store it in a central location before publication. As I thought about this side project, I looked at the tools that were out there. When I came across the website http://www.storytree.me/ , I was especially floored by the idea of being able to share stories with friends and family. When you have a memory to share as a story, you can post it with a photo and then invite other friends or family members to add to the story. The posts are presented as squares which are arranged vertically along a tree. As good as a tool as Story Tree was, it still seemed confining. For one, when you post inside Story Tree you are limiting yourself to their network and capabilities, where I wanted my project to be open. And, their sharing capabilities weren’t very flexible. So, I could send out invitations to friends via Facebook, but I couldn’t import my posts into a blog. So, I’m going to start a project which is similar to Experience Project without being locked down to just one social network, will invite almost anybody to share a story about their life or memory similar to Story Tree, and which produces content that can be viewed either online or as a compiled publication. I’m going to call it “Storybag,” although if anybody has an idea for a better name I’m open to suggestions. The goal of Storybag will simply be to compile stories into a format that is easy to share with an audience. Stories should mostly be nonfiction with a focus on writing about what’s going on in your life now, or maybe a past experience that you’d like to share. You can also write about something that’s happening in your community or maybe in the news. If you blog, you can submit your story to Storybag by simply sending me the URL for the blog post and I’ll make arrangements to grab a copy of your submission. If you are on Twitter or Facebook, we can talk about ways in which we could expand a post or series of posts into a longer submission, or maybe we would try publishing the threads as-is.

13/20

If you are on the Internet but don’t have a way to submit your story, you can write it as an email and send it to me. There will also soon be a blog where you can submit your story as a blog post. Submissions will be reviewed, edited, and fine-tuned before they go live on the Storybag blog and other, related social media sites. Then, they will be shared as a part of a monthly publication. So, that’s my general plan. Basically, it allows everyone to do what they normally do on Facebook–share news about their lives, exchange links to news stories, etc.–but it offers the opportunity to summarize what we’ve shared there and attach meaning. And when that happens, I’ll be able to prove that Steve was wrong.
View as a Blog Post:

http://iamjonmorgan.wordpress.com/2011/11/23/what-is-storybag/ Edit or Comment http://iamjonalanmorgan.wikispaces.com/What+is+Storybag%3F

14/20

What is Project Hover?
During the last four years, I’ve lived a double life. During the day, I was a mild-mannered Web Services Coordinator for a non-profit in Lansing called EduGuide. At night, in between my duties as a father and human dish washer, I have been quietly working on a plan to make it easier to produce, share, and curate content on the Internet. Which I guess means that I remained mildmannered. At first, my investigation into the flow of content was focussed around ways to easily convert content from one format to another. Back in the mid- to late 90′s when I began working as a professional web designer, a lot of my time was devoted to putting things up onto the Internet. For example, real estate listings, newspaper articles, membership directories, and ads. Nowadays, these are all things that you would just expect to be accessible online, but back then the Internet was new, and it wasn’t as easy to publish these kinds of materials on the Web. So I thought a lot about how easy it was now to publish resources on the web, but then wondered how that information might be converted and then published in an easily readable, printed format. Take, for example, real estate listings or articles from a newspaper. You can easily print these off, one by one, but then they aren’t associated together and the resulting pages aren’t very presentable. It seemed like there needed to be a way to design a publication so that it looked good on the web (or the screen) and on paper at the same time. I knew that the design needed to be minimal so that it was printer-friendly, but probably avoid columns so that the content was easy to read on the computer. I was inspired by Changethis, an organization which publishes manifestos as PDFs. These manifestos always consisted of a cover, and pages of content which were laid out in a way that made them easy to read either on the computer, or on paper. I began producing newsletters which followed some of the same rules as the manifestos. Then, over the last few years there have been different services which have launched which allow you to curate content using RSS. Some of my favorites have been Paper.li, and Zinepal. And, of course the rules have changed a lot thanks to social media networks such as Twitter, Facebook, MySpace, and Google+. I began to realize that my question shouldn’t be just about content readability and formats. Instead, I began to see that the publication is no longer important–that’s only a container. What matters is the content which goes into the container. Content should be designed so that it can be shared across several publications or social networks and shared on its own. The best explanation is that content should be considered to be fluid. The CD album is the best example of what I hope to accomplish. A band or a musician will get together to record twelve of their favorite songs, and then the songs are released to the public on an Album. Later on, the most popular songs from the twelve are re-released on a “Best of” CD. Maybe one of the songs has to do with Christmas, so that goes on a holiday compilation CD. Two of their songs appear in a movie, so they are included in the movie’s Soundtrack CD. At the same time, iTunes allows fans to pick-and-choose the songs they want to download. The songs are listened to individually or as a part of a customized playlist of favorite songs.

15/20

So, in the case of music CDs, it is the content–or the songs– that are important. They can appear in any album. My plan is to take a similar approach with written content. Start out with an article or an essay, and then distribute it or package it in as many ways as is feasible. I think that this is how someone will be able to reach the widest audience possible. I wasn’t sure what to call this initiative to think differently about the flow of content, so I decided on the broad name of “Project Hover.” Other than this blog, I manage three location-centered fan pages on Facebook: Shepherd Today, Marlette Today, and Hartland Today. I’ve used this pages to experiment with different ways to flow out content. I also maintain a personal Twitter account at @jnmrgn, and have started profiles on other social media sites. I recently launched a page for Project Hover on Google+.

View as a blog post: http://iamjonmorgan.wordpress.com/2011/11/23/what-is-project-hover/ Edit or comment: http://iamjonmorgan.wordpress.com/2011/11/23/what-is-project-hover/

16/20

Lifestyle

17/20

A Memorable Weekend
Whatever happens after today, this will always be remembered as the weekend when everything changed. Today we traded in our Windstar for a 2007 Cobalt. The vehicle is smaller than we’re used to, but it runs a lot better than our van did and actually has some additional amenities like a port for an MP3 player and remote start. We haven’t had car payments since back when we paid off the Windstar a few years ago, but it was a necessary evil if we wanted a dependable vehicle. As it was, my friend and co-worker Jenny had been doing twice her share of driving because we just couldn’t trust the van to get us from here to Lansing and back without giving us trouble. We also changed our travel plans. I was planning on driving the kids and myself to my parents’ house for Thanksgiving, but decided against it. Visits with our family for Christmas weren’t looking very possible either unless we either fixed or replaced the van. Fixing the van was always considered to be an option, but we had reached a point where it seemed like we were always throwing money to make a problem go away, only to discover there was a new problem. The time felt right to trade it in. So, on Thursday before we ate Thanksgiving dinner Theresa, the kids, and I stopped at a few nearby delaership to check out their stock of cars. The Cobalt was one of the cars that caught Theresa’s eye. After we returned home, I visited that delearship’s website and requested quotes for a few cars, including the Cobalt. On Friday we visited the dealership after Theresa got out of work and test drove the Cobalt with the kids in the backseat. By the time we returned with the car, we were ready to talk to the salesman about buying it. We ended up driving home in the car that night, and then returned today (Saturday) to finish the deal and sign the paper work. Read as a blog post: http://iamjonmorgan.wordpress.com/2011/11/27/a-memorable-weekend/ Edit or Leave a Comment: http://iamjonalanmorgan.wikispaces.com/A+Memorable+Weekend

18/20

Enjoying the Great Weather on Friday
I knew that the weather was going to be beautiful on Friday, but I didn’t know that the weather would be so perfect for a walk around the Shepherd Trail. I was grateful to be experiencing jacket weather on the day after Thanksgiving. As soon as I could, I fed the kids lunch and then got all of us outside as quickly as possible. We walked to the post office to get the mail, looked at cars in town, and then returned home. Next, I recruited the kids to help me re-organize our side of the garage so that there would be room for Theresa to park her car after the weather turned bad. I drained the garden hose, moved some of the bigger items to the side of the garage. Kayla cleared off the table she had been using for her wreath business. Kayla’s friend, Hannah, came over about an hour later. They played around outside, sometimes chasing Kayla’s younger brother, Josh, and sometimes tying him up for no apparent reason. It wasn’t long before Hannah’s sister, Hailey, showed up and then the three girls were tormenting (or chasing) poor Josh. I figured it was good for them to be outside when it was so good. And, Josh was getting tons of exercise. It seemed like the best thing we could do on a day like that was to walk around the Shepherd Trail. Since the start of November, it seemed like our warm days were numbered and the cold, snowy weather would be starting soon. So, I like taking every opportunity we could get to walk the trail. I’ve noticed that a lot of other people in town have been taking advantage of the warm weather by setting up their outdoors Christmas decorations. This seemed really smart. I also grabbed my camera and took some pictures during our walk. It seemed appropriate to catch the kids walking around the trail on what might be the last warm day of the year. Some highlights of our walk include Hannah teasing Josh about a girl he likes, and then Hailey teasing both Josh and Hannah at the same time (bold, but it was sure to stir up trouble). Also, for some reason Hailey kept telling Josh to hug every tree that we walked by, and for some other strange reason he would do it. When we passed a patch of cattails, the girls had to pick some so that they could throw “cattail bombs.” This was a trick that Hannah’s oldest sister, Adrienne, had shown us during a walk a couple of weeks ago. Break up the cattail in a couple of places to loosen the seeds, and then when you throw them they appear to explode. Josh and Hailey had run ahead, but came back to see what was going on and then they wanted to throw cattail bombs too. We stopped by the baseball diamonds where I took a shot of the kids together–something that looked easy, but it took several tries before I could get them while they were all looking at the camera. Both Hannah and Hailey wanted to try taking pictures, so I let them try with my camera as long as they were careful. My favorite pictures include the couple that Hannah took of me, and then the extreme close up shot that Hailey took of Hannah. When we resumed our walk, I tried to pick up the pace so everybody could get home at a decent time, and the kids and I could meet Theresa at the dealership.

19/20

Read as a Blog Post: http://iamjonmorgan.wordpress.com/2011/11/27/enjoying-the-great-weather-on-friday/ Edit or Leave a Comment: http://iamjonalanmorgan.wikispaces.com/Enjoying+the+Great+Weather+on+Friday

20/20

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close