When I manage projects for Bredemarket clients using Microsoft Excel, my workbooks contain targeted worksheets that may or may not interest all the client stakeholders. I’m finally recognizing this and acting accordingly.
Whether you use Excel or something else, data filtering always benefits your stakeholder customers.
A sample Excel project management workbook
Google Gemini.
Lately I’ve fallen into the habit of organizing Bredemarket client projects in Microsoft Excel. Why? Because my stakeholders (even in Google shops with Sheets) already have the software to read the files.
Excel and many other applications organize their data in one or more tabs (worksheets). Each tab features different data, presented in different ways at the discretion of the project manager. For example, a product marketing workbook may contain these worksheet tabs:
A summary view (Product Summary) of a product’s base offering, options, and prices.
A more detailed view (Product Detail) of the product base / option prices and costs.
An even more detailed view of certain supported features (Product Features) mapped to the base and options, along with detailed descriptions.
Candidate features for product versions (Candidate Features), and their statuses.
A view of prospects and the features they desire (Prospect Features), highlighting the desired features covered and not covered in the product.
You can see how all these worksheets could tie together. A prospect’s feature on the last tab that is approved and completed (double blind fingerprint verification) will ripple through all the other tabs. But an unapproved feature (geolocation in latitude-longitude at which a latent print was captured) would only appear on the last two tabs.
So what if recipients get more than the targeted worksheets?
Google Gemini.
Because of some things that have happened over a recent period, it finally penetrated my thick skull that just because all this data is critically important to ME to manage the project, some of it may bear no importance to OTHERS.
For example, the stakeholder that simply wants to know how much the product base and options cost doesn’t care about the features we never implemented for the Bullhead City Police Department.
At the same time, an outside developer is only interested in the features that we want to implement for the 1.3 release. Other than as background information, the developer doesn’t care which prospect(s) want the feature. And the developer doesn’t care—and perhaps shouldn’t even know (because privacy and security)—how much we price an option containing a particular feature.
Then I acted to only distribute targeted worksheets
Before all of this penetrated my thick skull, I would distribute entire workbooks and tell selected stakeholders to check the third and fourth worksheets and ignore the rest.
That’s dumb.
Why not give these selected stakeholders ONLY the targeted worksheets that are pertinent to them? More work for me to preserve the full view (all worksheet tabs) AND the targeted views, but much less work and much less confusion for the stakeholders.
I’m already doing this with one client. When it’s time to discuss features for future product releases, I’m only distributing the equivalent of the “Candidate Features” tab. This helps focus the discussion.
(I’m also filtering the rows that appear in the tab, but filtering is a topic for another discussion. And I’m also using Date of Last Update, Show/Hide, and conditional formatting as previously spoken by the wildebeest.)
In practice, and taking my 2022-developed Y2K-unfriendly document numbering system into account, I may store the following files in my client’s Microsoft or Google repository (or Bredemarket’s own):
BlueWidget2609a-All (all tabs, not distributed to anyone but kept on file)
BlueWidget2609a-ProductSummary (just the first tab, sent to Bob and Judy only)
BlueWidget2609a-CandidateFeatures (just the fourth tab, sent to Judy, Chris, and Tina)
What if I’m a REAL project manager and don’t use Excel?
Now I know some project managers tuned me out when I used the E word in the title.
But the same principle applies if you use Microsoft Project, or Microsoft Teams, or Asana, or Slack, or Jira, or InsaneBambi.AI.
(Whoops, InsaneBambi.AI is still embargoed. Forget I mentioned it.)
All of these apps support views, letting you create the equivalents of targeted worksheets so certain stakeholders only see certain things about the project.
Use your favorite app’s view capability to only display information necessary for your stakeholders.
Your stakeholders are your customers. Maintain a customer focus.
But what about you?
How do you curate project views for your stakeholders? Do you send filtered spreadsheets or rely on tool-specific dashboards? Let me know in the comments.
And if you have an identity, biometric, or technology product marketing project that could benefit from Bredemarket’s expertise, let’s talk.
The impressive AFIS purchased in 1998 but never implemented
I was a Printrak employee in 1998 when we signed a huge (for us) contract for US$45 million. We were a subcontractor to Siemens Nixdorf, but since the contract was for a national Automated Fingerprint Identification System, and Printrak built and sold Automated Fingerprint Identification Systems, our portion of the contract was substantial. Well, seemingly substantial; we’ll get to that.
And because Printrak was a publicly traded company (with the ticker symbol AFIS), I was certain the investor community would love this.
It didn’t. I recall that our stock price actually went down the day of the announcement.
But the system was still impressive. In those days most AFIS were law enforcement systems, although there were tentative efforts to use fingerperints for welfare benefits distribution. The Siemens-Printrak system for Argentina was something else entirely.
“When citizens enroll for a new ID card–the country already has an identification system–their fingerprints will be taken on paper, then scanned digitally and added to a massive database. They will then be issued a card with a bar code that will access their prints. These cards, available to all Argentine citizens, will be used to confirm their identity when they apply for jobs, school, immigration status and voting.”
Too bad it was never built.
Google Gemini.
The first issue: the cost
Part of the reason that the system was never built was because of a change of governments in Argentina. As later reported by the U.S. Department of Justice (I’ll say why DOJ got involved in a minute):
“In May 1999, according to the indictment, the Argentine government suspended the DNI [Documentos Nacionales de Identidad] project, due in part to instability in the local economy and an impending presidential election.”
A new government took power in that election, headed by Fernando de la Rúa. This new administration questioned the US$1 billion cost. (Printrak’s portion of the project was relatively small.) Eventually in May 2001 the entire project was terminated.
By that time Printrak was no longer an independent company, having been acquired by Motorola in 2000. But the people who didn’t buy Printrak stock in 1998 made the right decision.
They definitely did.
The second issue: the massive bribery scheme
This is out of scope for this particular Bredemarket post, which concentrates on companies that buy things and don’t use them, but there was an even bigger problem with the Siemens project. It turns out that Siemens officials paid more in bribes to Argentine officials (US$100 million) than the amount that Printrak was supposed to get (US$45 million).
“[D]uring the bidding and implementation phases of the project, the defendants and their co-conspirators caused Siemens to commit to paying nearly $100 million in bribes to sitting officials of the Argentine government, members of the opposition party and candidates for office who were likely to come to power during the performance of the project.”
(After the change in government) “members of the conspiracy allegedly committed Siemens to paying additional bribes to the incoming officials and to satisfying existing obligations to officials of the outgoing administration, many of whom remained in influential positions within the government.”
“When the project was terminated in May 2001, members of the conspiracy allegedly responded with a multi-faceted strategy to overcome the termination. According to the indictment, the conspirators sought to recover the anticipated proceeds of the DNI project, notwithstanding the termination, by causing Siemens AG to file a fraudulent arbitration claim against the Republic of Argentina in Washington, D.C. The claim alleged wrongful termination of the contract for the DNI project and demanded nearly $500 million in lost profits and expenses.”
“In four installments between 2002 and 2007, members of the conspiracy allegedly caused Siemens to pay approximately $28 million in further satisfaction of the obligations.”
This was not known until about a decade later, after guilty pleas in 2008 from Siemens and its Argentina subsidiary regarding criminal violations of the Foreign Corrupt Practice Act (the fraudulent arbitration claim), the 2011 indictment of eight former executives and agents of Siemens, the convictions of three of them (Truppel, Reichert, and Bock), and a civil settlement with a fourth (Sharef). The other four avoided setting foot in a U.S. courtroom because of extradition issues.
And all this took a long time. Reichert’s conviction occurred 20 years after the initial award.
But I seem to have strayed from my original topic.
When companies buy something but people never implement it
Forget everything I just said. For purposes of this post, the Argentine government spent a billion dollars on a system, and decided a few months later to not implement it.
This happens all too often. A company buys something and then says “nah.” Sometimes the company still has to pay for the product even though it never implemented it.
Why don’t companies buy something they paid for? I easily identified five fatal issues.
Issue 1: They bought it by mistake
In 2015 my then-employer MorphoTrak went through some significant transitions. One affected me personally: I moved out of proposals into strategic/product marketing. The others tangentially affected me, as two of my marketing superiors were informed that their services to MorphoTrak would no longer be needed after several months, and another marketing expert left a competitor and joined MorphoTrak.
At the time MorphoTrak had an annual contract with a services company. I won’t name the company, but when you put a heat source next to a block of ice, something happens. This annual contract had an auto-renew policy, and the company informed the known officials that this auto-renew was coming.
The known officials being the two marketing superiors who had already left MorphoTrak, and therefore never responded to the hot ice company.
Neither I nor the new executive from the competitor knew about the auto-renew policy. By the time I contacted the company and said we didn’t want to renew, the company icily informed me, “You already did.”
So I immediately cancelled the contract, ensuring that it wouldn’t auto renew a year later. And even though we were paying for nearly a year of the services, I never used them.
Issue 2: The users didn’t care what the company mandated
In theory, large organizations have a defined process for deciding which products to adopt, and which to not adopt.
For example (and this is based upon a real situation albeit anonymous), a company may mandate that all employees use Asana to track projects. The company buys a corporate Asana license covering all employees.
So an employee starts a project and tells the team that the work will be tracked in Asana.
The decision is not universally accepted.
“Asana sucks! Monday is much better!”
“I’m tracking all my stuff in Trello, and I’m not going to change platforms just for your dumb project!”
“Five years ago we used Microsoft Project for everything, I still use it, and the VP of Product loves my reports. If we don’t use Project she’ll ignore our work.”
“Why are you idiots using project management software? You can do this in Microsoft Excel. Just look at this-“
“A Redmond slave? You can do this in Google Sheets!”
“Can’t we just take care of this via email?”
Google Gemini.
So the Asana license sits unused as the project people use other means. Some already paid for by the company. Some via free versions. And some via purchases that their managers habitually approve.
Issue 3: No benefit to the employee
When decisions flow down, resistance flows up.
Let’s say management needs information about the work habits of hourly employees. Management wants this so they don’t overpay employees.
So management mandates a time clock system. When employees arrive at work they clock in. When they leave they clock out.
What benefit does this provide the employee? For some employees it actually hurts them. Jim the employee who habitually arrives at 8:05, or Grace the employee who habitually leaves at 4:55, actually lose from this new product.
Until Jim and Grace get together and start thinking.
When Grace arrives, she clocks in both herself and Jim before 8.
When Jim leaves, he clocks out both himself and Grace after 5.
Google Gemini.
And now you know why we have biometric time clocks.
Monica had been a latent examiner for 30 years when her boss made the announcement that the company had awarded the latest AFIS bid to NEC.
Which meant that Monica would no longer use the IDEMIA software. Successor to the MorphoTrak software. Successor to the Motorola software. Successor to the Printrak software.
Google Gemini.
Monica was then informed that mandatory training would take place in three months. Including how to place minutiae in the new system.
She muttered under her breath, saddened that she couldn’t retire in the next three months and avoid putting up with this nonsense.
Issue 5: Leadership doesn’t care about the new tool
But before Monica could stew over that, she received an urgent email from her boss.
“How many hours did you work last week?”
“45. I already entered them in Workday.”
Thankfully, Monica’s employer didn’t use time and attendance machines. You just entered your hours into the official corporate application, in this case Workday.
The boss then sent a follow-up.
“In the future, please send your hours to me via email.”
When leadership mandates a particular process (in this case to enter hours in Workday), but leadership itself doesn’t follow the process, employees get the message.
How do you get people to use mandated and purchased products?
I recently had a conversation with a services company that provides its services to secondary companies. In some cases, the company even donates the necessary hardware and software to the secondary companies.
Having no idea whether the secondary company will even use the donation, or let it gather dust.
For project success, you want adoption. Champions who will encourage others to use your product. Steps to remove roadblocks to using the product.
Internal go-to-market
This is why the best go-to-market projects have both an external AND an internal component.
Externally, the company has to convince prospects that the new product meets their needs and provides real benefits.
Internally, the company has to enable sales by explaining why the new product is important, how the prospects will benefit from it, and how sales itself will benefit by learning how to sell it.
If your go-to-market doesn’t address internal stakeholders, then they won’t learn how to sell or support your product, and the product willl fail.
Do you want your employees to push your new product? Bredemarket will apply its product marketing expertise to plan and provide both external and internal collateral for a go-to-market plan. Let’s talk about your needs and the possibilities.
I have worked with several companies’ content calendars over the years.
Two of Bredemarket’s clients are using Jira to manage their content calendars.
Another of Bredemarket’s clients doesn’t (as far as I know) have an official content calendar, but is tracking some content in a go-to-market Excel workbook.
If I remember correctly, MorphoTrak also used Excel for content management. MorphoTrak’s parent Morpho used a social media management platform, but I can’t remember which one.
At the time I was at Incode, the company used Asana to host its content calendar. (I have no idea how Incode has managed its content since May 2023.)
Bredemarket creates its own content (this is an example), and I also use Asana as my official content management platform.
Sharp-eyed people spotted how I worded that last sentence.
What did I just say?
If you read it again, you’ll see that I only discussed my OFFICIAL content management platform.
Some content, including this blog post/LinkedIn post/wherever else the text ends up, never gets logged in Asana. I just started writing it in iOS Notes and I will add various checkboxes up top as I share it on the blog and social channels.
Some other content, also not logged in Bredemarket’s Asana, is repeatable content that I store in Notes and repost periodically.
Something I post to my identity-related social channels (BIFS = Bredemarket Identity Firm Services).
And sometimes—a lot of the time, actually—I just go to a platform and WRITE stuff.
As a sole proprietor, I enjoy absolute control over Bredemarket’s messaging, and therefore the blog and social media approval process is very…streamlined. That isn’t the case elsewhere, where even a simple tweet requires approval. This makes it hard to live-tweet an event when the approver is unavailable…but there are workarounds. Perhaps I will reveal them one day.
What about process?
But if your corporate environment requires you to impose a strict content management structure, where all content is logged in the content calendar and all content requires approval, make sure that your content logging and approval process protects your company but DOESN’T silence it.
Because if your content approvals are too onerous, you will end up with no content at all.
Or you will end up with…perhaps I will reveal that one day.
I’ve previously discussed my writing process, which consists of a draft 0.5 which I normally don’t show to anyone, and then (preferably after sleeping on it) a draft 1 in which I hack a bunch of the junk out of draft 0.5 to streamline the messaging.
I need to apply that elsewhere.
Like my Gmail labels.
Creating a content calendar
Bredemarket just started providing content services for a new consulting client (no proposal or analysis services—yet), and one of my first tasks was to set up a shared content calendar for the client.
Keeping a content calendar in an email or a document or a workbook works, and I’ve done this before. But keeping it on an accessible, shared platform is better because everyone has the same view and you don’t have to worry about synchronization issues.
If you’re curious, the content calendar I set up has the following statuses:
Backlog
On Hold
To Do
Doing
Done
Bredemarket’s external content calendar is more complex, but that’s because I know that everything on that calendar goes through my iterative review cycle process, and because most of my external projects require an invoicing step at the end. So “Doing” involves a lot of sub-statuses before I’m “Done.” My client obviously didn’t need all this.
So I set up the content calendar, and the first issue (CC-1, create content calendar) is Done. (No confetti, Jira? Asana provides confetti.)
The problem is one of my other obsessive habits, labeling or tagging my emails so that I can easily find them.
All my content work for this client generates a lot of emails. And I decided that the best way to label these emails was with their Jira issue number.
So emails concerning the creation of the content calendar bear the label jiracc001.
And emails concerning another issue are labeled jiracc005.
Did I mention that we already have 28 Jira issues so far? (Mostly in the Backlog.)
I shudder to think what my email will look like a week from now. I will find the relevant emails, but will have to wade through dozens or hundreds of labels first.