Boss Wants Bitcoin in Treasury
Informal Executive Direction Without Governance
This memo is published by Bitcoin Treasury Analysis, an independent decision-record instrument for Bitcoin treasury governance.
Corporate treasury operations function within a delegation framework in which authority flows from the board of directors through executive officers to operational personnel. When a boss wants bitcoin in treasury and communicates that direction informally—through a conversation, an email, or a verbal instruction during a meeting—the subordinate officer who receives that direction confronts a governance condition that exists independently of the merits of the allocation itself. The condition concerns the gap between the authority under which the direction was issued and the authority under which the acquisition would need to be executed to produce a governance record that withstands subsequent review.
This memo describes the governance conditions under which informal executive direction to acquire bitcoin for corporate treasury intersects with the subordinate officer's personal exposure and the organization's authorization framework. It does not evaluate the merits of any allocation, prescribe conduct for any officer, or constitute legal advice regarding organizational authority structures. This memo covers the posture at a defined point in time.
Why Informal Direction Creates a Different Governance Condition Than Formal Authorization
Formal authorization for treasury actions follows a documented path. A board resolution specifies the parameters of the allocation, delegates execution authority to named officers, and establishes conditions under which the authorization operates. Meeting minutes record the deliberation. The officer who executes the transaction does so under documented authority that connects the operational act to the governance decision. If the transaction is later reviewed, the officer can point to the resolution, the delegation, and the parameters within which they acted.
Informal direction operates outside this documented path. An executive who instructs a subordinate to acquire bitcoin for the treasury may hold positional authority within the organization's hierarchy, but positional authority is not equivalent to governance authorization for a specific treasury action. The executive's instruction may reflect their personal conviction, a preliminary board discussion that did not result in formal action, a misunderstanding of the delegation framework, or a deliberate decision to bypass formal governance channels. From the subordinate officer's position, the source of the instruction is indistinguishable across these possibilities without access to the governance record that formal authorization would have created.
The governance condition that informal direction produces is one of ambiguous authority. The subordinate officer has received an instruction from a superior but does not possess documentation establishing that the instruction carries the authorization of the governing body. Execution under these conditions creates a transaction record that is not anchored to a governance act, producing a pattern that adversarial review may characterize as an unauthorized use of corporate funds rather than a legitimate treasury operation.
Personal Exposure for the Executing Officer
The officer who executes a bitcoin treasury acquisition bears personal responsibility for the transaction they initiate. This responsibility exists independently of who directed the acquisition. Under corporate governance frameworks, officers are expected to act within the scope of their authorized duties, and the scope of those duties is defined by the delegation framework that the board has established. An officer who executes a transaction that falls outside the scope of their documented authority—or that falls within a category requiring specific board authorization that has not been obtained—bears exposure that the directing executive's instruction does not eliminate.
This exposure attaches to the executing officer regardless of the outcome. A bitcoin acquisition that appreciates in value was still executed without proper authorization if the governance framework required board-level approval that was not obtained. Favorable outcomes do not retroactively create governance authorization. Conversely, an acquisition that loses value amplifies the consequences of the authorization gap because the loss generates the review under which the gap becomes visible. In either case, the executing officer's personal exposure stems from the absence of documented authority rather than from the financial outcome of the transaction.
The interpersonal dynamic compounds the governance condition. Subordinate officers who decline to execute instructions from superiors face professional consequences that the governance framework does not address. Career risk, relationship damage, and organizational marginalization are real consequences that operate outside the formal authority structure. The governance condition documented here does not resolve this tension; it identifies the personal exposure that execution under informal authority creates, which persists regardless of the professional consequences that non-execution may produce.
The Delegation Framework and Its Boundaries
Most corporate governance structures include a delegation framework that authorizes officers to conduct treasury operations within specified parameters. A chief financial officer may hold delegated authority to invest treasury funds in approved asset classes, within defined concentration limits, and using approved counterparties. Treasury staff may hold further-delegated authority to execute transactions within the parameters the CFO has established. These delegation chains create the operational flexibility necessary for routine treasury management while maintaining board oversight over the framework itself.
Bitcoin treasury acquisition tests the boundaries of existing delegation frameworks in several dimensions. The asset class may not appear in the list of approved instruments that the delegation framework specifies. Concentration limits designed for conventional treasury instruments may not address the volatility characteristics of bitcoin positions. Counterparty categories—exchanges, custodians, over-the-counter desks—may not match the categories that the existing delegation framework contemplates. Each of these boundary conditions creates a question about whether the existing delegation authority encompasses the directed action or whether the action requires specific authorization that the current framework does not provide.
When the boss wants bitcoin in treasury and the delegation framework does not clearly encompass the acquisition, the subordinate officer faces a governance condition in which the instruction exceeds the documented authority under which they operate. Execution under these conditions places the officer outside the delegation framework's boundaries, creating a personal exposure that the framework was designed to prevent. The exposure is not theoretical; it manifests when the transaction is reviewed by auditors, regulators, or litigation counterparties who examine whether the executing officer acted within the scope of documented authority.
What Escalation Produces in the Governance Record
Escalation—the act of routing the acquisition request through the formal governance process rather than executing it under informal direction—produces a governance record that serves the subordinate officer's interests regardless of the outcome. When the request is escalated, the governance process generates documentation at each stage. The executive's proposal is recorded. The board or committee receives the request, deliberates, and either authorizes or declines the allocation. If authorized, the delegation parameters are specified and the executing officer receives documented authority. If declined, the governance record reflects that the organization considered and rejected the allocation through its established process.
Each of these outcomes produces a governance artifact that the subordinate officer can reference under review. Authorization through formal channels creates the delegation documentation that justifies the officer's execution of the transaction. Declination through formal channels creates a record that the organization's governance process evaluated and rejected the allocation, insulating the officer from subsequent pressure to execute without authorization. Even a delay—a governance process that takes time to reach a decision—produces a record showing that the officer routed the request appropriately rather than acting on informal direction alone.
Escalation also redistributes accountability. Under informal direction, the accountability for the transaction concentrates on the executing officer and the directing executive, with no documented governance act distributing the decision across the authorizing body. Through formal channels, the authorization becomes a collective governance act, and the accountability distributes across the directors or committee members who participated in the decision. The executing officer's role shifts from decision-maker to implementer, and the governance record reflects that distinction.
What Compliance with Informal Direction Creates
An officer who executes a bitcoin treasury acquisition based solely on informal executive direction creates a governance record with specific characteristics. The transaction appears in the organization's financial records. The counterparty records reflect the officer's authorization of the transaction. Banking records document the movement of funds. Custody records show the organization's acquisition of bitcoin. Each of these operational records exists, but none of them connects to a governance act that authorized the acquisition through the organization's formal decision-making process.
Under routine conditions, this gap may remain invisible. The organization holds the bitcoin, the position appears in treasury reports, and the absence of formal authorization does not generate immediate consequences. Visibility emerges when the transaction is examined—during an audit, in response to a regulatory inquiry, in the discovery process of litigation, or during board review triggered by adverse performance. At each of these review points, the examiner traces the transaction to its authorization, and the trail leads to an informal instruction rather than a governance act.
The officer who executed the transaction occupies a specific position in this review. They are the person whose name appears on the transaction records, whose authority was used to initiate the acquisition, and whose operational acts created the position. The informal instruction from the executive may be documented in an email or may exist only as an unrecorded conversation. In either case, the governance record does not reflect that the board authorized the acquisition, that the delegation framework encompassed it, or that the executing officer acted within the scope of documented authority. This absence defines the officer's personal exposure under review.
The Record That Informal Direction Leaves Behind
Informal direction does not disappear from the organizational record; it persists in forms that are less structured and less favorable than formal governance documentation. Email threads in which the executive directs the acquisition create discoverable records that establish the chain of instruction but not the chain of authorization. Calendar entries, meeting notes, and message logs may corroborate that the direction was given. Colleagues who were present during verbal instructions may provide testimony. Each of these evidentiary fragments reconstructs the informal direction while simultaneously demonstrating that formal authorization was absent.
Under adversarial review, this reconstructed record serves a different function than formal governance documentation would. Formal documentation establishes that the organization authorized the action through its governance process. Reconstructed informal direction establishes that an individual executive instructed a subordinate to act outside the governance process. The first characterization positions the acquisition as an institutional act; the second positions it as an unauthorized act that two individuals undertook without the governing body's documented approval. The distinction is material in fiduciary analysis, regulatory evaluation, and litigation.
Assessment Outcome
When a boss wants bitcoin in treasury and communicates that direction informally to a subordinate officer, the governance condition that results differs materially from one in which the allocation proceeds through formal authorization channels. Informal direction creates a transaction record disconnected from a governance act, concentrates personal exposure on the executing officer, and produces an evidentiary trail that adversarial review may characterize as unauthorized action rather than institutional decision-making.
Escalation through formal governance channels produces documentation that connects the transaction to a governance act, distributes accountability across the authorizing body, and positions the executing officer as an implementer of documented institutional authority rather than an independent actor responding to informal instruction. The governance record that each pathway produces persists beyond the transaction itself and defines the evidentiary posture under any subsequent review.
Operating Constraints
This memorandum assumes a corporate governance structure in which material treasury decisions require board-level or committee-level authorization and in which subordinate officers operate within a documented delegation framework. Organizations with different authority structures, without formal delegation policies, or in jurisdictions where officer liability attaches under different standards face different conditions. The analysis does not prescribe conduct for any officer, does not constitute legal advice regarding organizational authority, and does not evaluate the adequacy of any specific delegation framework. The documented conditions reflect the posture when this analysis was completed and remain interpretable within the scope under which the record was produced.
Framework References
Should My Company Buy Bitcoin?
Relevant Scenario Contexts
Nonprofit — Considering (5M) →
Bootstrapped Saas — Re Evaluating (5M) →
← Return to Bitcoin Treasury Analysis
Explore Related Scenario Contexts →
The risk is often not the decision itself, but the absence of a durable record explaining how it was made.
Generate Decision Record$995 · 12-month access · Unlimited analyses
A Bitcoin Treasury Decision Record is a formal governance document that classifies an organization's readiness to allocate Bitcoin as a treasury asset and records the basis for that classification under a defined standard.
View a completed Decision Record →