Prime Pixels IT Services

Loading

Archives 2026

A percentage change can look dramatic when the underlying count is small. Comparisons also become misleading when date ranges or data coverage differ.

The decision to make

Compare like-for-like periods and show absolute values alongside the change. Explain incomplete or delayed data before interpreting a trend.

Practical checklist

  • Check equal period lengths and relevant weekdays.
  • Show the before and after counts.
  • Review missing data and tracking changes.

An illustrative example

A change from one click to zero is a recorded decrease, but it does not establish a sustained performance collapse.

Your next step

Use additional periods and related metrics before choosing a major intervention based on a small movement.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

A dashboard is useful when its metrics support a decision. Displaying every available number can hide the information that requires action.

The decision to make

Start with the decision-maker and the question they need answered. Define each metric, source and update interval before designing cards.

Practical checklist

  • Write the business question for every chart.
  • Distinguish totals, unique counts and rates.
  • Show the reporting period and data coverage.

An illustrative example

Visitors, sessions and page views are different measures. Labelling all of them as customers creates a misleading picture.

Your next step

Remove metrics that do not inform an action and provide enough context to interpret the remaining ones correctly.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

A trial should have a clear start, duration and end state. Customers need to know what remains available and what requires an upgrade.

The decision to make

Enforce expiry using server time and the agreed eligibility policy. Do not rely on a browser countdown or cosmetic blur to protect restricted results.

Practical checklist

  • Explain the trial limits before signup.
  • Check access to old results and exports after expiry.
  • Define how eligibility is evaluated without making unsupported identity assumptions.

An illustrative example

If results require a paid plan after expiry, the API must enforce that rule as well as the dashboard.

Your next step

Test the final trial day, expired access and a legitimate upgrade so customers receive consistent behaviour.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

A failed payment is a state transition that needs clear communication and controlled access. Immediate deletion of customer work is rarely a sensible default.

The decision to make

Define retry, grace-period and cancellation behaviour according to the agreed product policy and provider capabilities. Keep billing status separate from assumptions about payment arrival.

Practical checklist

  • Process verified provider events.
  • Show the customer a safe billing recovery route.
  • Reconcile application status with the payment provider.

An illustrative example

A delayed event should not accidentally extend access forever or cancel a customer whose payment succeeded elsewhere.

Your next step

Document the lifecycle and test the transitions without charging a real customer unintentionally.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

A plan table is only a promise until the product enforces its limits. Entitlements must describe exactly what customers can use and when usage resets.

The decision to make

Separate feature access, resource counts and consumption limits. Define upgrade, downgrade and expiry behaviour before implementing checkout.

Practical checklist

  • Specify site, member and usage limits.
  • Enforce limits on the server.
  • Explain remaining access after a plan change.

An illustrative example

A five-site plan should not allow a sixth site through a direct API call simply because the interface disables its button.

Your next step

Test each plan boundary with real application requests and make the customer-facing wording match the enforced rules.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

A customer portal must prevent one organisation from accessing another's records. Correct filtering in one dashboard does not prove isolation everywhere.

The decision to make

Trace tenant identity through APIs, exports, background jobs and file downloads. Never trust an organisation identifier merely because the browser sent it.

Practical checklist

  • Create separate test organisations.
  • Attempt cross-organisation reads and writes.
  • Check reports, cached responses and downloadable files.

An illustrative example

A report endpoint can leak information even if the main page is secure. Include secondary routes and queued tasks in the review.

Your next step

Keep repeatable isolation tests tied to the authorization rules and run them when data-access behaviour changes.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

Roles should reflect responsibilities rather than simply offering admin and everyone else. Excessive access can expose customer data or allow unintended changes.

The decision to make

List actions and data separately, then assign the minimum access needed for each role. Apply checks on the server, not only by hiding buttons.

Practical checklist

  • Map viewing, editing and billing permissions.
  • Test access across customer organisations.
  • Document who can invite and remove members.

An illustrative example

An accounts employee may need invoices without access to operational customer records. A single broad administrator role may be unnecessary.

Your next step

Review the role matrix with the customer and test denied actions as carefully as permitted ones.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

A roadmap should distinguish observed problems from untested requests. The loudest feature suggestion may not solve the most consequential user difficulty.

The decision to make

Group feedback by the task and affected audience. Review frequency, impact and implementation dependencies without pretending every request has equal value.

Practical checklist

  • Record the underlying problem and examples.
  • Compare with usage and support evidence where available.
  • Define how a release will be evaluated.

An illustrative example

Several requests for a new export format might actually indicate that customers cannot share existing reports conveniently.

Your next step

Prioritise a clear problem statement and expected user outcome before committing to a specific interface or delivery date.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

Onboarding should help a customer reach a useful result. Asking for every possible setting before showing any value can delay understanding and increase abandonment.

The decision to make

Separate necessary setup from optional enrichment. Explain the benefit of each required connection and provide honest alternatives when data is unavailable.

Practical checklist

  • Identify the first useful task.
  • Allow safe defaults for nonessential settings.
  • Show progress and a recovery route when setup fails.

An illustrative example

A website tool can offer a public-page audit before a customer connects search data, while clearly explaining the limits of that initial result.

Your next step

Measure completion of the useful task rather than counting account creation alone as activation.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

Acceptance criteria turn a feature name into observable behaviour. Without them, a screen can look complete while important states remain undefined.

The decision to make

Describe inputs, permissions, results and failure cases. Use examples that a reviewer can execute without guessing the intended behaviour.

Practical checklist

  • Specify who may perform the action.
  • Define the saved result and visible confirmation.
  • Include invalid input and repeated requests.

An illustrative example

For a team invitation, acceptance includes expiry, an existing member and an unauthorised inviter, not just an email field and button.

Your next step

Attach the criteria to the feature before implementation and record the results during release verification.

AI-assisted planning guide published by Prime Pixels. Examples are illustrative, not customer case studies. Project scope and applicable requirements must be checked for your circumstances.

Enable Notifications OK No thanks