Monthly Archives: May 2016

Kids, Project Management & the Serenity Prayer

by
Serenity-Prayer

Source: https://www.goodnightjournal.com/wp-content/uploads/2014/02/serenity-prayer005.jpg

I’m not religious by any stretch of the imagination, but I do believe in the Serenity Prayer. It’s something I have to remind myself of often as I interact with both my kids and my projects. It provides a level of grounding. What’s the point of getting frustrated if it’s outside my control?

The nature of my personality requires that I be hands on. I want to be involved. I want to help control the outcome. But the nature of many of my projects results in things outside my control. These projects are big and complex integration projects that involve technical resources both within my organization and often within the client; and business users. Often the decision to move forward with this implementation was handled by resources higher up the corporate food chain. This means there are questions, considerations and discovery that need to take place at the beginning. The inner workings of corporate culture and the organizational power hierarchy become evident here. It is usually at this time when a decision is made that is totally outside your control, but has major impact on the project. It may be a decision to user an external intermediary for some piece, or the implementation of a business process that impacts overall timelines.

My initial inclination is to get frustrated. It’s that overwhelming feeling of wondering how you are going to accomplish what you set out to do if you don’t control all the pieces. After a little while, I remind myself that I can’t worry about things outside of my control. These are things that I can’t change. So what can I do?

  • Accept the things I can not change – Most importantly, I can recognize and remind myself that there a components of the project that I do not control, and can not change. This allows me to keep my sanity during the project implementation.
  • Establish Trust – I can establish trust with whomever is involved in the project and do my best to work together towards the overall success of the project.
  • Communicate  – I can engage fully with the entire project team and make sure everyone knows the status. There is some trial and error that needs to happen to determine the appropriate level of communication.
  • Raise Concerns & Questions – I can monitor the project situation and raise concerns & questions to the appropriate team members.
  • Focus on what I can control – It’s my job to be looking at the entire picture. What can I contribute? What ideas or actions can I bring to the table to facilitate project implementation success?

This approach is one I need to do a better job of also applying to my children. In some ways it easier to apply this to a project and people you are professionally affiliated with rather than your kids. I think the principles are the same. Yes, your kids belong to you. However, they have their own personalities and natural characteristics which combine with their unique nurtured experiences that we need to consider. I need to keep reminding myself of this as I work to establish & maintain trust, openly communicate, raise concerns & questions and focus on what I can control while encouraging them to do the same.

Make sure you apply what your expertise to your own practice

by
captain_obvious

Source: https://twitter.com/obviouscapn

I strongly believe in documentation. As a project manger, I feel that’s I am in the best position to properly capture the twists and turns along the project path. Given this, it makes the most sense for me to at least do the initial drafts of the documentation. There may be times where technical resources need to provide more details around how something is implemented, but for the most part I know enough to provide the starting point. This applies to both business documentation and ongoing production support documentation. I consider this core to what I do as a professional when I manage any project, at work or on volunteer initiatives. After quitting one job, I stayed on for another 3 months to hire my replacement and ensure the documentation was complete and up to date. Three years later, after some personnel turnover, I was asked to come back as a subject matter expert. I resurrected this documentation, refreshed it and used it as the basis for addressing the questions.

Despite all that, my biggest take away from last week’s DrupalCon was that my business needs process to scale. Yes, I know that it’s obvious. I do this all the time for my client work, ensuring that someone could take over my projects with relative ease. In those scenarios, someone taking over would find an archive of project artifacts previously provided to the customer, a site with the project details including other relevant reference sources. The outstanding work would be documented per the client request (i.e. task lists, service tickets, etc).

I have even started this for processes that are outside of my core competencies. If it was new, I needed to document the process for me and my partner so we could reference it, measure it and update it as required. It’s all the other stuff I haven’t documented. To continue the example of someone taking over my client work, while they have the tools, they won’t have the instruction guide. They won’t know how I go about a project. They won’t know how often I communicate with the client or in what form. There won’t be a guide for what to do the first day they step in.

It’s disturbing that the things that are most obvious to us are often the things we overlook the most. Regardless of how valuable we think we are, we have to plan for the unexpected. This could range from tragedy like sickness or death or joyful opportunities like extended holidays in locales with limited connectivity (yes, those places still exist). We limit ourselves when we only share our talents externally. We need to also apply our expertise to our broader roles and organizations. In my scenario, building these processes for how I do what I do will allow my company to grow. For yours, you are adding value not just to external customers, but also creating significant value for the organizations we engage with.

I hope after reading this you think about your core competencies and whether you are truly practicing what you preach.

 

Recap & Top Lessons Learned from DrupalCon New Orleans

by

DrupalCon New Orleans was the epitome of “work hard, play hard.” The days were spent in intensive, thought provoking sessions, the nights were spent at the multitude of social events.

Business Summit

Monday was spent as expected, at the Business Summit. Susan Rust coordinated this year’s event and focused on 3 key areas: recurring & repeat revenue, killer marketing & new clients and leading with ease. The day was planned with presentations by corporate industry leaders followed by small group discussions and subsequent presentation of the key take-aways.

While the information was interesting and valuable, the business summit tended to raise more questions than provided answers for us as a micro-business. For example,

  • How do you ensure that you don’t exert too much emotional (or other) investment on too few customers?
    • How do you do this when the same resources are working in and on the business?
  • Do you find or grow your talent? And how do you do this without distracting from the revenue that keeps your business afloat?

Two critical sentiments resonated with me for most of the conference:

  1. Scaling your business is about process, tools & business infrastructure.
  2. Spending too much time working in the business will prevent you from long-term health & success.

We closed out the day by attending the Opening Reception and started collecting our DrupalCon swag (for me it was t-shirts and some awesome drupal socks).

Conference Session

Tuesday was the official opening of the conference. It started with some early morning global entertainment with costumes, Drupal parodies & skits followed by the official kick-off keynote by Dries Buytaert.

My first session was all about data structures in Drupal. This is a pretty fundamental component, and plays to my internal data geek, so I thought it would be a good place to start my technical Drupal education. Ron Northcutt did a good job of describing the structures and providing guidelines for making better decisions. If you ever get tripped up on the terminology or want a starting point in your Drupal education, this presentation would be good for you to watch.

For the remainder of the day, I stuck mostly to the business track. I attended the critical metrics for your drupal business session, hosted by Michael Silverman (DUO) and Dave Terry (Media Current). These guys dove into resources, tips and metrics we should all understand and track for our businesses. Some key points and resources include:

  • Know your goal or exit plan from the beginning
  • “Master the Rockefeller Habits: What You Must Do to Increase the Value of Your Growing Firm” by Verne Harnish
  • “Drive: The Surprising Truth About What Motivates Us” by Daniel Pink
  • “Traction: Get a Grip on Your Business” by Gino Wickman
  • Don’t forget to measure your culture (presentation highlights ways to do this)
  • To scale your business, you need to be accounting on an accrual basis
  • Sales Tools: Geckoboard, CRMs, templates
  • “A Win Without Pitching Manifesto” by Blair Enns
  • Recruting Tools: JAZZ, DISC, Perform Yard
  • “TopGrading” by Brandford D. Smart
  • “Bo’s Lasting Lessons” by Bo Schembechler
  • “How to Win Friends and Influence People” by Dale Carnegie

I also attended Jeff Walpole’s session on why and how enterprises get involved in the open source community and the drupal showcase GE and FFW case study. I briefly attended the birds of a feather “BOF” (adhoc session) for small drupal shops before I had to head over to the Women in Drupal event. Approximately 200 people showed up before heading off to the other parties.

On Wednesday, I played hooky in the morning before attending Jeffrey “Jam” McGuire’s session on the value of Drupal 8 technical features. This was incredibly valuable to me and I would recommend taking the time to watch this presentation if you aren’t already immersed in Drupal 8. I also attended the diversity in tech session by Nikki Stevens and Karyn Cassio. They shared valuable stats and practical actions we can control in our own behavior, before opening the floor for an honest discussion.

Thursday is the official last day of the conference so is a bit shorter, leaving room for the closing ceremonies and time for contribution sprints. I attended Aimee Degnan’s session on prioritizing your scrum product backlog for Drupal work. The focus was balancing “keeping the lights on” with new product features for a site or group of sites over time. The biggest insight for me had more to do with how to apply a similar model to working on the business and working in the business.

  • Your business (like a single site) is comprised of: primary value creation; supporting systems with direct impact to value creation and supporting systems with indirect impact to primary value creation.
  • Like a project, there is some overhead associated with running your business as well as the application and review of reporting.

We often apply agile methodologies to our projects, but we haven’t been as effective on applying them to our business.

The next session was Jody Hamilton’s talk on growing your own talent. Jody shared her experiences build Zivtech’s talent. She provided tactical tools & tips on on-ramping, quality, recruitment methodologies and evaluations. The key to doing this successfully is process. The biggest argument small shops have for not pursuing this is struggling to balance workload capacity with training resources. Jody challenged this assumption, pointing out that focusing on the work at hand is a short-term initiative. For long-term viability of your business, it’s imperative to think long-term.

  • Developing the talent to keep your culture, philosophy and work are a requirement to scale your business.

My final session selection was easy. I attended Susan Rust’s margins & maseratis talk. There were so many key points in this talk that I think you’ll need to watch it. Susan started with these 3 directives for successfully scaling your business:

  • Be data driven
  • Measure over time
  • Develop processes

From a practical perspective, I learned we have a lot to do including:

  • Documenting everything we do to deliver value to clients
  • Document the tools we use to do them, measure them, report on them (yes, document ALL the tools..)
  • Measure everything..per project, per person, per organization
  • Make sure to focus (aka specialize). Don’t be everything to everyone.
  • It’s all about the margins! Businesses that want to grow focus on revenue where businesses that want to scale focus on margin. It’s not that revenue isn’t important, but it’s more about changes in revenue that are most critical.

And lastly, we attended the closing ceremonies and the Drupal 6 funeral procession, with brass band and police escorts as we shut down New Orleans streets.

I hope you’ve enjoyed my adventure at DrupalCon New Orleans. I know from others that there are quite a few sessions I missed. I’m planning on watching the recordings of those over the next couple of weeks. I’d also love to hear about your experience and take aways.

Preparing for my First Drupalcon

by

I’m heading to my first Drupalcon in New Orleans next week. While I’m a very technical project manager who has worked on website implementation projects with content management systems or other integrations, I’ve never worked in or on a Drupal project. This is really my husband’s area of expertise.  Carson has been to several Drupalcons, but still spent quite a bit of time debating between the business and technical track. You can read his blog post on it if you’re interested in his thoughts. I struggled a bit with my own planning so I am hoping a blog post on it would help organize my own thoughts.

I attended Drupal GovCon last year where I participated in mostly the business sessions. I wrote about that experience too. Going into this Drupalcon, I have many of the same goals that I had last summer: learn more about Drupal and make some good contacts in the Drupal community. As I was looking through the different sessions, I did not want to hyper-focus on any one particular track as I have personal & professional interests in business, project management, women in drupal and the learning more about the technical side of Drupal. I’m not sure this aligns to the typical attendee. This made my initial pass through the different sessions a bit frustrating. I walked away thinking that there wasn’t a lot of sessions that interested me and concerned that I would be wasting my time. I was a bit more successful the second time around, and by that time the Birds of Feather “BOF” (adhoc sessions) were available.

Monday was easy! Carson participated in the business summit at last year’s Drupalcon and got a lot out of it. This year I’m participating in it, while he attends the government summit.  This is a great opportunity to learn from other Drupal agencies. Businesses in the Drupal community tend to really open up their books and processes and experiences in a way that other businesses don’t. I attribute that to the core principles of giving back if you participate in the open source community.

On Tuesday, I’m mixing up technical sessions with business ones. After my first Dries keynote, I start off my day with a session on understanding data structures and am definitely going to the session on how to get more involved in the open source community. Beyond that, I’m still bouncing between critical metrics for your business and teaching drupal to kids; case study on leveraging drupal to deliver business results beyond clicks, conversions & revenue and building a remote drupal shop. I’m also going to the BOF for small business owners to share ideas. Then we’ll head over to the Women in Drupal event we’re sponsoring.

Wednesday is focused on the business side of things. I’m hoping the writing great case studies for drupal.org will allow me to pick up some skills for writing great case studies for anyone. Then I’ll be learning about selling the value of new drupal 8 technical features, and finding my purpose as a drupal agency. There is only one time slot where I have not decided yet. Is it the session on Drupal community as an example of diversity in tech or implementing performance metrics and dashboards for your digital agency or productive collaboration of sales and project management as a means to drive customer satisfaction? Before we head off for more socializing, I’ll participate in the account management to customer success evolution BOF.

Thursday is the last day of sessions. I’m going to learn about successful drupal integrations then focus on growing talent & margins within your organization.

I am excited to participate and think I came up with a good schedule. Lucky for me, I’m not locked into any one of these and can easily bounce between sessions as the floor plan  & timing permits.