Marketing

Today I received a purchase order from a new client. I received a purchase order because one of my colleagues had quoted a project and provided a proposal that met this new client’s needs and expectations.

The reason we were able to write the proposal, was that I had built a relationship with a decision maker, a millennial professional, in this generational business .

The reason I was able to build a relationship, all by phone and email, was because I’d had some conversations about his business, his markets, and his emerging needs.

The reason I was able to have some conversations is that I had posted a relevant Blog article through Glass Magazine to my LinkedIn social media feed. This Blog article on Delegated Design and Experience vs Inexperience, struck a chord with him and he sent me a well-thought response about his pain points, needs, observations. It resonated with him. It spoke to almost his exact experience.

When he sent me the message I replied instantly; within the hour. I used my mobile phone, while working remotely in Florida, to respond in writing to him, and then to call him. We arranged further discussion by phone prior to a strategic board meeting he had. He wanted to communicate the prospects of working together to his board and the “why” behind it; the value proposition; the idea prompted by he Blog. I couldn’t have posted the Blog, without this particular venue and platform being provided by Glass Magazine.

This is an example of marketing today. In telling a story. In making a real connection with someone. In provided relevant content and value. In giving more than is received. The purchase order was just the manifestation, the end result, of the process. It was as a result of the trust, knowledge, and good will built during the process.

I wasn’t interested in “the sale.” I was interested in the relationship.

This is one face of marketing. It is an example of inbound marketing; content marketing. It’s not what I do, it’s part of who I am. It’s the same for you, if you will allow it.

Workflow and Development

There are two basic forms of “workflow” or “new practice” development:

  • That which we create (innovation and new category.) This needs to bring value to clients and they become part “creative partner” with us (from a “what if” and testing scenario).
  • That which our clients require (get competent and optimize)
    • They define
    • We build/design to spec
    • We execute
  • The Truth moving into the future
    • We all need in our businesses to develop one or both of these.
    • It needs to be done while being connected to the market; with the user/client

The details, the building, the success of the service or product, is up to the builders and operators

Project Psychology

There is much said and written about Project Management. Every project is to have (among other things) :

  1. A PMP: Project Management Plan
  2. A RMP: Risk Management Plan

What about a “CCP” and a “PPP”?

  1. CCP: Client Communication plan
  2. PPP: Project Psychology Plan

You see, each client and each project has unique needs, wants and desires, best identified in the Proposal stage of the project, but manifested throughout. This is true at “B2B” (business to business) level and “P2P” (person to person). You see, also, each project has a “mind” of it’s own; multiple constituents within the context of the project, differing goals and values, some within our sphere and some outside of it. So often projects become “triage mode” or “tyranny of the urgent” because we are focused on “checking the boxes” and not dealing with the essence, the mindsets, the commitments of others, the “psychology” of the project.

The more we align with client expectations, understand the dynamics of the project, the mindsets, the conflicting priorities, the more our “box checking” effort (within our process) is just a matter of consequence and documentation. Because “checking the box” within our processes doesn’t deal with “the why’s” within each project. It only memorializes activities.

How’s our understanding of project and people dynamics? This has influence over the quality of a project manager’s life and the quality of project produced.

Compressed construction 

I mean REALLY compressed. Rarely works.

There are many brilliantly crafted plans on paper that have no allowance for the unexpected, for supply chain issues, for unintended consequences, or poor execution by someone or some organization along the way. Plus the single biggest issue I’ve seen and experienced over and over again that leads to challenges from the outset, is simply delayed decision making, and delayed release of contracts.

Compressed construction requires concurrent, collaborative, (shared-reality) communication; cultural alignment, confidence in each other and in the enterprises involved, and it requires everyone to follow through on the decisions and tasks in their domain within the proper timelines. It can’t be done with the old “throwing it over the wall mentality.” Each decision and event is not “someone else’s problem.” It’s everyone’s problem. This teamwork is difficult to achieve and it requires commitment from all parties, and to be led by the GC or CM.

The thing that happens most often in compressed construction schedules is erosion of relationship, poor profitability, and a project that still takes the time “it needs” to take to get finished. This often results in an unhappy owner asking questions due to failed expectations vs. promised goals and deliverables.

I’ll offer some solutions and suggestions on a future blog.

Post Project Meetings – Defining Experience

Post project review meetings are arguably the most important project and team meetings in an organization (and a required SOP now at my company) since it defines lessons learned; what we did well, what we did not, how we can improve. It helps identify “the experience” of the team and the client. It’s ALL about the client’s “experience.” The team’s experience is equally important  (client experience is only as good as the team experience and service to each other)

There’s many hotels, restaurants, auto dealers, contractors, engineering firms, professional services corps, ALL TOUTING the SAME THING.

Which one’s do you like to frequent and write checks to? Those with whom you have a positive experience or a negative experience ? Positive experience (gratitude, smiles, fair price, great value, delivering on what has been promised) means repeat business and growth.

Post project reviews are necessary for company and professional advancement.

All progress starts by telling the truth. These meetings are great truth revealers and tellers. We learn and grow through doing, celebrating wins, and fixing problems.

Fast and Cheap?

This was my response to client today (after several emails) requesting us to give our best price for a quick turn and schedule critical project:

I want to be very clear. Best price and immediate start/quick turn do not go together. Quick turn with quality, and fair price for the situation go together. It’s not “fast and cheap”. It’s fast and commensurate with service.

I don’t like to work like my hair is on fire. That happens enough in this biz every day

We will look at what we can do, how or where it can plug in, how quickly we can get it done for you and your team, and let you know. We always like to provide
value, timeliness, and a reasonable approach with the work to our clients
.”

Their response?

“Amen. Good words. You’ll see an RFP soon”

Be clear. Be true. Be candid. Be respectful. Provide value. People appreciate clarity and it makes it easier to improve our ROI on proposals and sales.

What to Say

Prior to our December staff meeting I wrote this to key colleagues helping me to prepare for the meeting. Sometimes we need to just put it out there. The feedback I got was so meaningful and led to a great meeting and connectivity.

“You know me, normally I have much to say. But I’ve been so deep into the dirt and operations, and I am so fatigued mentally, that I am struggling to even have or organize a message. It’s not often we can all meet in staff meeting, so it’s critical that any message is clear and delivered well. So I need to lean on RS, DP, GR, and you for insight and input. If I could say what I want to say, I am not sure if I would say:

1. Thank you. Thanks to everyone on staff and all our colleagues. Companies are only as good and as happy as their people. Thank you all for everything you do day to day to care.

2. Merry Christmas. Happy holidays. Enjoy your family. We are not our work, it’s just what we do and how we try to bring value to the world.

3. Have Debra to tell everyone what we’ve distributed in 401k match this year to help people in the FUTURE to have an income stream after they retire, and to update on any benefits.

4. Let everyone know we have 6 people in NC and they just celebrated year 6 anniversary.

5. That we need their inputs and engagement in all of their realms to make the company better and to improve service to clients.

6. That I value and care about each person

7. That 2018 can be our best year ever

8. That transparency and vulnerability is some of the magic in bringing strength and connection to relationships

I don’t know what to say. Maybe all of the above or maybe none. You all tell me and we will all come together prior.”

This dialogue opened the door for such good inputs, and a really good meeting. I love our people. We are all in the same boat. We all have to row together.

What’s your message?

Solution Sets 

Schedule & budget are also determining factors in a solution set and in providing problem solving and deliverables to clients. It’s not “provide solutions at any cost and for as much time as they take.” Also speed of response, speed of performance, and prompt project delivery almost always win, and are typically the top or near the top priority for clients.

It’s hard as technical professionals sometimes to consider budget and schedule as equal variables or boundary conditions with other more direct technical issues.

We’ve got to ask ourselves “how can I get this done in the allotted time frame and budget” and use that as part of the boundary conditions around the solution and deliverable.

When we do this on every project and task within the project, it mitigates loss, makes the potentially marginal job profitable, and makes the good one really great.

Every person, on every team, at every level should have this reality in mind. They should be accountable, and also empowered, to call timeout and to take action with the project leaders and principals.

And it means not being a slave to the defined technical and software processes when there’s an issue slowing us down. Remember, procedure and technical tools are supposed to serve us, not the opposite. These days that often gets reversed, spending more time on the process and software functionality than we spend on the problem or creative aspect of the solution.

Provide serviceable solutions while staying in business.

Drawing the line 

One of the constituents on a project I’m working on recently established an extreme position in regards to a proposed solution; very extreme. Their position and proposed consequence has impact on a large, broad body of people, user groups, and businesses. The goal from the  owner was collaboration and shared solution. What they got from this particular group was the opposite.

The problem with an extreme position is that when we make a statement and proposed consequence, we’ve got to be willing and able  to back it up. “If you don’t do this, I’m going to do _________ (fill in the blank.)” 

Are you REALLY going to do that?

Sometimes a clear line needs to be drawn. Think and be mindful about where you draw it. You’ll have to back it up when someone challenges you on it.

Dissent

Allow dissenting voice in meetings, especially around strategic discussions and direction. If  dissent doesn’t define this idea clearly, call it “allowing opposing viewpoints.” Some will say “I’m playing the devil’s advocate for a moment.” Phrasing aside, I find it good to appoint someone to state the “cons”, to point out the roadblocks, to take the opposite view, to articulate the worst case scenario. I’m not always excited about the opposing view. In fact for many years I didn’t think it necessary to hear, nor did I advocate for it. It made me uncomfortable. It still does at times. This is good. It allows freedom for all to vent their perspective and be heard. Collaboration in decision making wins. I’ve made many mistakes alone or in isolated decisions. Again, collaboration wins. Dissent and opposing viewpoints are one key part of that process. All stakeholders must voice input. In the end, the leader makes the decision, but  it’s harder to make the wrong one when all the facts are on the table and we are fully informed.