Concorder Enterprise Hub
Workspace for teams and SMBs evaluating digital stacks, product roadmaps, and HR policies. Each prop...
Proposals
Members
Internal mobility 2026: build skills in-house or hire for speed?
We keep seeing the same pattern: a team needs a skill urgently, hiring takes longer than planned, and existing employees feel stuck watching opportunities go elsewhere. At the same time, not every role can be filled internally, and some teams genuinely need senior expertise quickly.This proposal is about how we want to balance internal mobility and external hiring in 2026. The best answer is rarely “always promote” or “always hire”. We need a policy that makes it easier to move talented people into the right roles, while still letting teams hire when the business would otherwise stall.We are choosing one operating model for the year. Each model includes a practical set of commitments: how managers plan headcount, how employees access opportunities, and how we handle backfilling so mobility does not become a hidden tax on the teams that develop talent.Clear rules that reduce politics and last-minute exceptionsFaster staffing for priority projectsHigher retention of high performersManagers still feel supported when they lose strong peopleComments should focus on where our process currently breaks, for example approval bottlenecks, lack of visibility into openings, or fear of losing talent without replacement.
Company offsite 2026: pick dates, city, and a purpose
We want an offsite that feels worth the time and travel. When offsites fail, it’s usually because they become a packed agenda without real decisions, or because logistics overwhelm the experience. When they work, people come back with a shared picture of the year, sharper cross-team relationships, and a short list of commitments that actually stick.This proposal separates three things that are often mixed together: timing, place, and purpose. The dates matter because they affect attendance and energy. The city matters because it shapes travel time and costs. The purpose matters because it determines whether the agenda should be discussion-heavy, workshop-heavy, or simply relationship-heavy.The offsite window in 2026The host city for the gatheringThe main purpose statement that should guide the agenda designVote on the window and city options, then choose the purpose that best matches what the company needs right now. Comments are welcome for practical constraints, especially travel time, visa concerns, or accessibility needs.
Company generative AI policy: which governance model should we adopt?
Many organizations are moving from experimentation with generative AI to everyday use in drafting, summarizing, coding, customer support, and analytics. That shift creates new risks: data leakage, hallucinated outputs, IP and confidentiality issues, security threats, and unclear accountability for decisions influenced by AI-generated content.What this proposal asks you to vote onContext: genAI adoption is fast, governance must catch upGovernance model: Choose a policy tier that matches our risk tolerance and operational reality.Tooling approach: Decide whether we limit work to approved systems or allow public tools under strict rules.Controls: Select the baseline safeguards we implement across departments.Use comments to list real use cases (marketing copy, HR templates, code suggestions, customer emails), identify the data types involved, and flag compliance constraints. The best option will be the one that enables value while controlling risk consistently.NIST’s AI Risk Management Framework (AI RMF) provides a voluntary structure for managing AI risk across the lifecycle. NIST has also published a Generative AI Profile to help organizations identify and address risks that are particularly relevant to generative systems. This proposal turns that guidance into an internal decision: what governance model should our company adopt right now, and what controls are non-negotiable?The objective is not to slow innovation. The objective is to make genAI use safe, auditable, and aligned with business goals—so teams can adopt tools confidently, customers are protected, and leadership can demonstrate responsible oversight.
Company AI offsite: set dates and location for policy rollout
Context: turning genAI experimentation into accountable practiceMany teams already use generative AI for drafting, summarizing, research assistance, and code suggestions. The challenge is that informal adoption can outpace governance: inconsistent rules, unclear accountability, and uneven training. A short, structured offsite can accelerate alignment—especially if it produces a practical policy, a training plan, and a clear list of approved tools and approved use cases.This proposal schedules a focused internal offsite to finalize and launch the company’s generative AI policy. The program should cover: safe use expectations, prohibited data categories, human review requirements, escalation for high-risk use cases, and an implementation timeline for logging/auditability in business-critical workflows. The content is designed to align with NIST’s AI Risk Management Framework and the NIST Generative AI Profile, which emphasize structured risk management across thThe vote is split into two functional decisions (dates and location) so people can signal multiple workable options. After voting, leadership can select the best-supported combination and proceed with booking and calendar holds.What this proposal asks you to vote onDates: select the offsite date range that works.Location: select the venue that best supports an intensive working session.Use comments to propose agenda topics and flag any compliance constraints that should shape the final policy.
Ticketing tool 2026: platform choice and migration window
Choosing a platform must come with a realistic migration plan: data import, integrations (SSO, CRM, knowledge base), training, and staged go-live. This proposal showcases Concorder by combining ranked approval of platform approaches, a multi-select vote for mandatory requirements, and a date-range vote for migration windows to visualise timeline impact.Rank the platform options, select required capabilities, and choose all migration windows that are feasible. In comments: list must-have integrations (SSO, Slack/Teams, email, CRM) and top current pain points (prioritisation, escalations, reporting).In 2026 we want to standardise a ticketing tool for internal support (IT/HR/Facilities) and/or customer support. Today we have fragmentation: email queues, spreadsheets, and different tools by team—slowing response times, weakening SLA measurement, and increasing manual work.ContextWhat we’re decidingWhich ticketing platform approach to adopt (fit + governance)Which requirements are non-negotiable (SLA, reporting, integrations)Which migration window minimises operational riskHow to participate
Hybrid work policy 2026: model choice and pilot period
ContextWhat we’re decidingWhich hybrid model to adopt (cadence-based, role-based, or activity-based)How long the pilot should run and what success looks likeWhich minimum rules must apply (right to disconnect, meeting norms, space booking)How to participateIn 2026 we want to formalise a hybrid work policy that reduces ambiguity (who is onsite, when, and for what) while improving collaboration without losing flexibility. Common friction points include poorly planned hybrid meetings, “empty office days,” and perceived fairness differences between roles.The right model depends on how work gets done: some functions benefit more from in-person time (onboarding, complex reviews, customer-facing sessions), while others can operate more remotely. To demonstrate Concorder’s mixed-option flexibility, each model includes an explicit pilot date range, optional attachments (policy references), and pros/cons to capture operational trade-offs.Rank the hybrid models. Then select all non-negotiable principles you want in the policy. In comments: share constraints (time zones, customer schedules) and propose 2–3 simple KPIs (onboarding time, perceived productivity, meeting effectiveness).