Make it easier to activate members

Make it easier to activate members.

Our strength is already here: members, locals, staff and the relationships built over time. The next chapter connects that strength more clearly. Useful information. A familiar face. A next step that fits. Less time finding our way; more time doing the work.

Find. Know. Reach. Act.

The portfolio’s new experience is a working proposal with fictional data—not a live NJEA service. Find a source. Explore a role-appropriate dashboard. Choose what is useful. Preview a practical next step. The sequence connects communications work without asking members to understand the technology behind it.

Try the four-part experience →

One trusted foundation; different responsibilities.

Local leaders need useful local context. Field representatives need a view of assigned locals and opportunities to support them. County leaders need appropriate aggregates. The goal is a more informed conversation—not ranking locals or labeling individual members based on clicks.

Production access belongs on the server. A role selector is not security. Tableau supports row-level approaches, including server-enforced data policies; embedding and licensing need to be agreed with IS. Tableau security documentation.

A useful video has a useful next step.

Brightcove is already part of NJEA’s work, according to the portfolio brief. The opportunity is to connect a captioned video and transcript to a current resource, an event or a person. Its documented Campaign 2.0 Salesforce integration is for VOD; it does not automatically establish a Marketing Cloud Engagement connection. Brightcove documentation.

Cvent’s Salesforce integration can expose attendee and event history. Marketing Cloud Connect is a separate connection with product and permission prerequisites. Actual NJEA entitlements, mappings and consent rules need confirmation. Cvent · Salesforce.

WordPress today. A thoughtful decision tomorrow.

Keep local identity, strong content, familiar publishing and staff expertise. Communications shapes the member experience; IS leads secure architecture; Membership stewards authoritative identity. Different source systems can have clear authority for different records. OneNJEA does not need to become a giant photo filesystem for those records to work together.

Relevance should be a choice.

Let members select topics, channels and a region. Explain recommendations, keep a way to browse everything, and make opting out easy. The portfolio uses fictional service and training examples. It does not use GPS, social profiles, inferred beliefs or political targeting.

App, PWA—or both?

Test the task first: accessible sign-in, saved resources, useful reminders, appropriate offline behavior and a reliable next step. An installed web app may help; a native app may justify itself for particular device needs. WebKit documents permission-based push for home-screen web apps, but real device testing remains essential. The portfolio phone is a preview, not an installed app. WebKit documentation.

Measure service, not just activity.

Task completion, useful search results, current resources, accessible journeys and successful handoffs are meaningful measures. Opens, views, clicks and attendance are observations—not proof of understanding, agreement or causation. Public and protected views of governed data have different responsibilities.